@SebasTEAan @alyx givn that my current ISP has enormous lag spikes even on #IPv4 even if I ere to use a #GIFtunnel to FRA, that would increase latency and would add #geoblocking woes as well as more instability to it.

• And I certainly see no reason to cough up the cost of @ripencc membership & getting a PI address space when I think it should be the responsibility of @BNetzA to mandate #DualStack connectivity with #LowLatency!

@tschaefer
1&1 with Roaming #VodafoneNL #Dualstack works. #IPv6only without #NAT64 works too.

@pmevzek @landley I wish I had this luxury.

• Cuz I often have to deal with fucked-up networks that are #IPv4only and sometimes going #DualStack is flatout not being allowed and even having #IPv6 at the public-facing side is seen as a problem.

And I'm more often than not not the guy who gets to make that decision.

• I was only able to get IPv6 allowed WAN-side at one place after my employer encountered the problem that some workers have shitty #CGNAT that bricks #OpenVPN so they could not #VPN to the HQ.

@drscriptt again: I'd see this as more error-prone than #DNSSEC and only hindering the transition from #IPv4 to #IPv6 if not bricking proper #DualStack…

@net_gremlin

1. Obviously...
2. Not gonna argue with that.
3. as long as there are #IPv4only services and applications, I do at least need proper #DualStack. Regulators like @BNetzA refuse to mandate #IPv6 connectivity and I only get #IPv4 from my #ISP.

• I guess some day I'll be forced to get a @ripencc membership just to get a Provider-Independent allocation.

@dickenhobelix ich hätte auch gern mindestens nen /64 zu.meinrm /28.

• Kriege aber kein #DualStack vom #ISP!

@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!

@fusl @mnalis @0xF21D

I do that with #pfSense & #OPNsense (depending on the exact network in question) and have it merge multiple sources that get cached.

In total, I do may out the 30 DNS servers and whilst I have #IPv4only, I have everything ready for #DualStack (#IPv4 + #IPv6) once my ISP stops keeing it's thumbs um their ass...

@krzym @fuchsiii solange @BNetzA nicht mindestens ein /64 an #IPv6 pro #IPv4 vorschreibt wird sich nix dran ändern.

• Erst wenn #DualStack flächendeckend ist kann IPv4 abgeschaltet werden!

@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!!!

@jue @goetz @fluepke Until you have some #remote workers who only have #CGNAT + pseudo-static #IPv6 addresses on a #consumer line...

Then it's not an option and you'll have to resort to #RFC1918 and #DualStack #WAN-side, as I had to setup for a fmr. employer / client...

@kkarhan

"mandate proper #DualStack support" (for all) is nonsense

@fluepke sadly the only way this could be changed if @BNetzA would mandate proper #DualStack support.

• And I'd welcome it if they were to mandate a /64 per IPv4 if not a /48 of #IPv6's per #IPv4 block allocation...

I just don't expect this to happen from the same agency that would rather #subsidize #Starlink that mandate #FTTB & #FTTH coverage and installations...