#tunnelbroker — Public Fediverse posts

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.

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.

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.

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.

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.

Was ich gar nicht wußte: Bei #Vodafone bekommt man mittlerweile einfach so ein /64, ohne das irgendwo beantragen zu müssen.
Und es funktioniert noch dazu, kein Gehampel mit #tunnelbroker mehr, der #Mikrotik macht das sauber inklusive Sonderlocken wie "ignoriere die Nameserver, die Vodafone Dir aufs Auge drücken möchte, nimm den #pihole!"

#ipv6 wie es sein soll. Na gut, größer als /64 bekomme ich als Privatkunde wohl nicht, d.h, #Vlans im Heimnetz gehen dann eben nicht, jedenfalls nicht mit v6.
Irgendwas ist ja immer, für jetzt bin ich zufrieden.

@volpeon @puniko IMHO #IPv6's notation should've been #decimal like #IPv4 so the entire IPv4 address space would've fit as a #subnet into it, providing us with a transition mechanism that would've allowed backwards compatibility by virtue of addressing every port as a dedicaded IPv6, enabling way faster adoption.

Sadly until EVERYTHING supports IPv6 natively and comes with fixed prefixes (at least a /64 on mobile) that are statically allocated, I can't even use it.

There's a reason I've got a /28 of IPv4's but by ISP won't even delegate me a /48 of IPv6's: Because there is neither demand nor offer for that.

And yes, HE.net's #Tunnelbroker isn't solving issues because even if I choose a PoP in Germany everyone will just blatantly #GeoIP (which on it's own should be illegal IMHO!) one to the #USA, worsening the entire experience by virtue of illegal #Adware and #Tracking...

I set up the #hurricaneelectric #tunnelbroker in #openwrt according to https://openwrt.org/docs/guide-user/network/ipv6/ipv6tunnel-luci - but RX/TX in the interface view stays at 0, and I can't ping my tunnel endpoint either.

Do I need some additional firewall rules? tcpdump with filtering the IPv4 endpoint address doesn't show anything either.

Does openwrt connect at all? mh...

@stefano Adoption of #IPv6 isn't a widespread problem any more... (there are some dinosaur #IPv4-only networks, but they're slowly dying...)

But: I'm not fine with what I get from an #ISP as a private consumer. I want the option to have a fixed prefix, I want to be able to get #RDNS delegation for that prefix.

That's why I currently ignore what my ISP gives me and instead use #HurricaneElectric's #Tunnelbroker for my IPv6 connectivity. It's free and offers the features I want 🙄