@dlakelan @tschaefer sadly #OpenWRT isn't an option in my case.

The problem is rather due to my ISP being incompetent and lazy assholes, and unless you have someone who can kick some asses around Vodafone Germany I doubt that...

• And until I got stable #IPv6 #WAN-side there's no point doing it #LAN-side either, because it'll only make applications crash that prefer IPv6 and will refuse to go #DualStack or #IPv4 once they got an IPv6 (because for some reason the devs assumed everyone will only have #CGNAT / #DualStackLite scenarios, and not the opposite of that I guess)...

Yes, this annoys me the hell out of it too!

@mook @0xIO32

like obviously ipv4 is a pain, but it's also not that big a deal either it's a legacy thing

There are still devices & software being manufactured & sold that are #IPv4only and will refuse to work if they don't have a static #IPv4 on #WAN.

• And I'm not talking solely about #Devkits and #Enterprise-#Licensing…

#IPv6 is sadly not yet mandated otherwise #CGNAT & bs like #DualStackLite would've never been created.

@landley @jschauma @ryanc @0xabad1dea yeah, the exhaustion problem would've been shoved back with a #64bit or sufficiently delayed by a 40bit number.

Unless we also hate #NAT and expect every device to have a unique static #IP (which is a #privacy nightmare at best that "#PrivacyExtensions" barely fixed.)

• I mean they could've also gone the #DECnet approach and use the #EUI48 / #MAC-Address (or #EUI64) as static addressing system, but that would've made #vendors and not #ISPs the powerful forces of allocation. (Similar to how technically the #ICCID dictates #GSM / #4G / #5G access and not the #IMEI unless places like Australia ban imported devices.

I guess using a #128bit address space was inspired by #ZFS doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...

• Personally I've only had headaches with #IPv6 because not only do I only have #IPv4only #Internet but my #ISP refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of #IPv4's in with my contract!)and stuff like #HurricaneElectric / #HEnet's #Tunnelbroker fail face first due to #Geoblocking and the fact that #ASNs get geolocated, not their #PoPs...

If I was @BNetzA I would've mandated #DualStack and banned #CGNAT (or at least the use of CGNAT in #RFC1918 address spaces) as well as #DualStackLite!

@tschaefer fängt damit an dass bis heute nicht alle #IPv6 haben oder bekommen können...

• Bspw.: Verweigert mein #ISP die Bereitstellung von echtem #DualStack. (Deshalb kann ich diesen Post auch nicht direkt aufrufen!)

Umgekehrt sind bis heute nicht alle #Diensteanbieter & Services von #IPv4 auf #IPv6 migriert worden.

• #IPv6only ist anders als ein #Windows-Verbot (was #BDSG & #DSGVO eigentlich verlangen!) illusorisch.

Sorgt zwar für Henne-Ei-Problem, wäre aber durch die @BNetzA lösbar indem diese zwangsweise je IPv4 mindestens ein /64 an IPv6 vorschreibt und Bullshit wie #CGNAT [insbesondere mit #RFC1918-Addressraum] verbietet!

• Besonders Bullshit wie #DualStackLite ist murks: Entweder korrekt Dual-Stack oder lasst es sein!!!