@tschaefer ich habe eher Bedarf nach #NAT46 in #Deutschland.

• #Tunnelbroker von #HurricaneElectric wird wegen #ASN auch in #FRA als #USA von Dritten #geolocated & #geoblocked!

A new headscratcher: in VyOS, a #6in4 tunnel (eg HE #TunnelBroker) the tunnel's source IPv4 address can be set to 0.0.0.0, to mean that egress tunnel traffic will use the src IPv4 from the interface going to the tunnel endpoint. This is helpful when that IP is DHCP assigned.

But in FreeBSD, gif(4) disallows 0.0.0.0, requiring an IP to listen for tunnel traffic. Presumably, gif doesn't want to listen on all interfaces.

My solution: dhclient-script(8) to configure gif once binding a DHCP addr.

@neu3no @halva yes and no.

• I can see the benefit of a miniaturized retro gaming system (I think legacy systems need to be served with properly maintained software & hardware).

https://www.youtube.com/watch?v=2P1E2vjpcRo
https://www.youtube.com/watch?v=B8WfiRRvQXo

As with #IPv4 the problem is that there is no mandate to provide users with static prefixes and I'm stuck on a /28 of IPv4's and can't even get a singoe /64.

• And before you ask: No, #Tunnelbroker is not a valid solution as HE.net's tunnel will get #USA #GeoIP'd even eith the PoP in FRA so it bricks a shitload of things due to #Geoblocking and bad #peering. Believe me, I tried that already!

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

@shoppingtonz @alternativeto @torproject also every #Tunneling - regardless if #SSH or #VPN or whatever - will inevitably introduce #latency (unless you happen to be customer of a shitty #ISP with horrible #peering and thus can cut down on hops needed, which is AFAIK only a theoretical scenario)...

• Outside of circumventing #Geoblocking and bypassing #IP-based #Banning (i.e. for #Cheating) I've not seen any use-cases.

In fact I stopped using #HEnet #Tunnelbroker and #IPv6-#GIF-Tunneling because it created more issued than it solved on my #IPv4only #Internet connection…