Scoopta

joined 2 years ago
[–] Scoopta@programming.dev 1 points 1 day ago (1 children)

Wahhh, sorry. Jeroba timed out while making the post, and I know sometimes when it does that it posts anyway so I normally check...and I did this time as well, but it didn't show up so I figured it had actually failed...and it hadn't...ughhhh.

[–] Scoopta@programming.dev 1 points 2 days ago (3 children)

I have seen some fields that are weird but I don't see a problem with the android one? Well I guess calling it rolling isn't quite right but otherwise it's pretty accurate

[–] Scoopta@programming.dev 4 points 2 days ago

Technology is literally never complete, especially when it's code based on reverse engineering of a proprietary format...

[–] Scoopta@programming.dev 13 points 2 days ago

WebUSB was always an insane idea to me. The web has just gotten ridiculous

[–] Scoopta@programming.dev 1 points 3 days ago

I just never left 100% native (apt in my case). I have been trying to make the switch to 100% flatpak...but it's so painful that I just haven't.

[–] Scoopta@programming.dev 1 points 4 days ago

I'll be honest, less ugly than NAT which is really where I draw the line (I hate NAT), especially if they're charging you per /64, that's borderline diabolical from a hosting provider. If I was getting charged per /64 I'd probably route /96s too. Lack of SLAAC is unfortunate though.

[–] Scoopta@programming.dev 1 points 4 days ago (2 children)

No, you still need a gateway, maybe what you're referring to is the lack of NAT? But that honestly makes it less confusing, there's still a default gateway though. It's funny you say the subnetting thing because for me it's the opposite. In v4 subnets are variable sized, sure /24 is the most common but I've found everything from /8 all the way to /29 in the wild. In v6...every subnet in a sane network is a /64, it's practically enforced by the standard. You basically can't go smaller and going bigger is pointless. That means the first 4 hex groups are your subnet, the last 4 are the device, basically always. Now VPNs are one of the few environments where /64 isn't super heavily enforced and you can go smaller but it's still good practice to use it anyway. Memorizing addresses is...you're not wrong, but also I personally don't find it that bad and here's why. The first half of the address isn't THAT much longer than a v4 address. It is a bit, and yes it's hex so letters. Thing is, the first half is the bit you can't control, kinda equivalent to your public v4, so once you memorize that, the second half can be whatever you want and as short as you want. Worst case you can always use DNS to avoid memorizing addresses but that does require extra configuration.

[–] Scoopta@programming.dev 2 points 4 days ago (4 children)

I'm not sure what you mean by that? What problems specifically?

[–] Scoopta@programming.dev 2 points 4 days ago

🤔, I'm not sure what would cause it to break other than a misconfiguration, my setup isn't stock though, my most recent endeavor was migrating to a VTless system, so I do a lot of "different" and non-conventional things. Sure I've had configs break but it's because I made a mistake, that's not the init's fault.

[–] Scoopta@programming.dev 6 points 4 days ago (6 children)

Yeah, right now in order to do it without giving up a bunch of services you have to combine it with NAT64+DNS64. NAT64 maps the entire IPv4 space to a /96 of your chosing and then DNS64 will generate AAAA records based on that /96 when upstream doesn't provide one so clients can talk pure v6 even to v4 only sites. There are some services (steam client and discord voice calls) that require v4 addressing and won't work with this setup, but it gets you 98% of the way there.

[–] Scoopta@programming.dev 8 points 5 days ago (9 children)

I don't use either 🤔

 

Are there any currently available RISC-V dev boards that support the H extension for running KVM?

 

TIL that apparently capital one was assigned the entire 2630::/16 block...which is the largest assignment I've seen to date. Does anyone know of other absolutely massive allocations...are there even any others this large?

 

I've been using duckduckgo for years ever since I degoogled but I'm increasingly annoyed by its complete lack of IPv6 connectivity. I use NAT64 and so it works fine but it bothers me to use services that don't have v6. Does someone have a good non-google IPv6 search engine that's privacy respecting?

1
submitted 2 years ago* (last edited 2 years ago) by Scoopta@programming.dev to c/ipv6@lemmy.world
 

I'm curious about something so I'm going to throw this thought experiment out here. For some background I run a pure IPv6 network and dove into v6 ignoring any v4 baggage so this is more of a devils advocate question than anything I genuinely believe.

Onto the question, why should I run a /64 subnet and waste all those addresses as opposed to running a /96 or even a /112?

  1. It breaks SLAAC and Android

let's assume I don't care for whatever reason and I'm content with DHCP, maybe android actually supports DHCP in this alternate universe

  1. It breaks RFC3306 aka Unicast-prefix-based multicast groups

No applications I care about are impacted by this breakage

  1. It violates the purity of the spec

I don't care

What advantages does running a /64 provide over smaller subnets? Especially subnets like a /96 where address count still far exceeds usage so filling subnets remains impossible.

view more: next ›