#6in4 — 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.

Сделал себе виртуальный IPv6, который не даёт провайдер, через технологию #6in4. Как я понял, это сродни прокси/ВПН, то есть создаёшь себе виртуальный туннель, подключаешься к нему и начинают работать ресурсы, доступные только для IPv6. Открывается, правда, не всё почему-то 🙄

Зарегистрировался и настроил виртуальный адрес через провайдера tunnelbroker

Сделал себе виртуальный IPv6, который не даёт провайдер, через технологию #6in4. Как я понял, это сродни прокси/ВПН, то есть создаёшь себе виртуальный туннель, подключаешься к нему и начинают работать ресурсы, доступные только для IPv6. Открывается, правда, не всё почему-то 🙄

Зарегистрировался и настроил виртуальный адрес через провайдера tunnelbroker

Сделал себе виртуальный IPv6, который не даёт провайдер, через технологию #6in4. Как я понял, это сродни прокси/ВПН, то есть создаёшь себе виртуальный туннель, подключаешься к нему и начинают работать ресурсы, доступные только для IPv6. Открывается, правда, не всё почему-то 🙄

Зарегистрировался и настроил виртуальный адрес через провайдера tunnelbroker

Сделал себе виртуальный IPv6, который не даёт провайдер, через технологию #6in4. Как я понял, это сродни прокси/ВПН, то есть создаёшь себе виртуальный туннель, подключаешься к нему и начинают работать ресурсы, доступные только для IPv6. Открывается, правда, не всё почему-то 🙄

Зарегистрировался и настроил виртуальный адрес через провайдера tunnelbroker

Сделал себе виртуальный IPv6, который не даёт провайдер, через технологию #6in4. Как я понял, это сродни прокси/ВПН, то есть создаёшь себе виртуальный туннель, подключаешься к нему и начинают работать ресурсы, доступные только для IPv6. Открывается, правда, не всё почему-то 🙄

Зарегистрировался и настроил виртуальный адрес через провайдера tunnelbroker

Shitty #vodafone not only being #IPv4 only when you run their router in bridge mode, but also actively blocking #6in4 almost feels like a deliberate act to sabotage #IPv6 usage...

Shitty #vodafone not only being #IPv4 only when you run their router in bridge mode, but also actively blocking #6in4 almost feels like a deliberate act to sabotage #IPv6 usage...

Shitty #vodafone not only being #IPv4 only when you run their router in bridge mode, but also actively blocking #6in4 almost feels like a deliberate act to sabotage #IPv6 usage...

Shitty #vodafone not only being #IPv4 only when you run their router in bridge mode, but also actively blocking #6in4 almost feels like a deliberate act to sabotage #IPv6 usage...

Shitty #vodafone not only being #IPv4 only when you run their router in bridge mode, but also actively blocking #6in4 almost feels like a deliberate act to sabotage #IPv6 usage...

Hello everyone!
I have set up a #6in4 tunnel on my server with /56 subnet to have an #ipv6 /64 subnet for my router.
Everything works well but this setup consists of a tun interface with specific settings and also from some ip route rules and iptables rules.
My question is how do I make it persistent?
I know how to save iptables rules but I have no idea on how to save ip route rules and a tun configuration.
I have done this with a 6to4 script from github and cannot repeat the same manually without any helper scripts.

Any help will be appreciated.
Thanks in advance.

#linux #askfedi #selfhosted

Hello everyone!
I have set up a #6in4 tunnel on my server with /56 subnet to have an #ipv6 /64 subnet for my router.
Everything works well but this setup consists of a tun interface with specific settings and also from some ip route rules and iptables rules.
My question is how do I make it persistent?
I know how to save iptables rules but I have no idea on how to save ip route rules and a tun configuration.
I have done this with a 6to4 script from github and cannot repeat the same manually without any helper scripts.

Any help will be appreciated.
Thanks in advance.

#linux #askfedi #selfhosted

Hello everyone!
I have set up a #6in4 tunnel on my server with /56 subnet to have an #ipv6 /64 subnet for my router.
Everything works well but this setup consists of a tun interface with specific settings and also from some ip route rules and iptables rules.
My question is how do I make it persistent?
I know how to save iptables rules but I have no idea on how to save ip route rules and a tun configuration.
I have done this with a 6to4 script from github and cannot repeat the same manually without any helper scripts.

Any help will be appreciated.
Thanks in advance.

#linux #askfedi #selfhosted

Hello everyone!
I have set up a #6in4 tunnel on my server with /56 subnet to have an #ipv6 /64 subnet for my router.
Everything works well but this setup consists of a tun interface with specific settings and also from some ip route rules and iptables rules.
My question is how do I make it persistent?
I know how to save iptables rules but I have no idea on how to save ip route rules and a tun configuration.
I have done this with a 6to4 script from github and cannot repeat the same manually without any helper scripts.

Any help will be appreciated.
Thanks in advance.

#linux #askfedi #self_hosted

Hello everyone!
I have set up a #6in4 tunnel on my server with /56 subnet to have an #ipv6 /64 subnet for my router.
Everything works well but this setup consists of a tun interface with specific settings and also from some ip route rules and iptables rules.
My question is how do I make it persistent?
I know how to save iptables rules but I have no idea on how to save ip route rules and a tun configuration.
I have done this with a 6to4 script from github and cannot repeat the same manually without any helper scripts.

Any help will be appreciated.
Thanks in advance.

#linux #askfedi #selfhosted

Hat noch jemand Probleme mit 6in4 Tunneln auf Fritzboxen seit Update auf FritzOS 7.50 beobachtet? Seit dem Update „ruckelt“ es, Verbindungsabbrüche und lange Ladezeiten
#IPv6 #Tunnel #6in4 #FritzBox 5530 #FritzOS #Netzwerk

Hat noch jemand Probleme mit 6in4 Tunneln auf Fritzboxen seit Update auf FritzOS 7.50 beobachtet? Seit dem Update „ruckelt“ es, Verbindungsabbrüche und lange Ladezeiten
#IPv6 #Tunnel #6in4 #FritzBox 5530 #FritzOS #Netzwerk

Hat noch jemand Probleme mit 6in4 Tunneln auf Fritzboxen seit Update auf FritzOS 7.50 beobachtet? Seit dem Update „ruckelt“ es, Verbindungsabbrüche und lange Ladezeiten
#IPv6 #Tunnel #6in4 #FritzBox 5530 #FritzOS #Netzwerk

Hat noch jemand Probleme mit 6in4 Tunneln auf Fritzboxen seit Update auf FritzOS 7.50 beobachtet? Seit dem Update „ruckelt“ es, Verbindungsabbrüche und lange Ladezeiten
#IPv6 #Tunnel #6in4 #FritzBox 5530 #FritzOS #Netzwerk

Hat noch jemand Probleme mit 6in4 Tunneln auf Fritzboxen seit Update auf FritzOS 7.50 beobachtet? Seit dem Update „ruckelt“ es, Verbindungsabbrüche und lange Ladezeiten
#IPv6 #Tunnel #6in4 #FritzBox 5530 #FritzOS #Netzwerk

Set up a #6in4 tunnel on my router with HurricaneElectric and now my #ipv6 works fine. So I'm going to go ahead and assume this is a problem at #XMission and not specifically the router.

Tunnel doesn't have a lot of bandwidth though, so probably going to be very temporary.

Set up a #6in4 tunnel on my router with HurricaneElectric and now my #ipv6 works fine. So I'm going to go ahead and assume this is a problem at #XMission and not specifically the router.

Tunnel doesn't have a lot of bandwidth though, so probably going to be very temporary.

Set up a #6in4 tunnel on my router with HurricaneElectric and now my #ipv6 works fine. So I'm going to go ahead and assume this is a problem at #XMission and not specifically the router.

Tunnel doesn't have a lot of bandwidth though, so probably going to be very temporary.

Set up a #6in4 tunnel on my router with HurricaneElectric and now my #ipv6 works fine. So I'm going to go ahead and assume this is a problem at #XMission and not specifically the router.

Tunnel doesn't have a lot of bandwidth though, so probably going to be very temporary.

Set up a #6in4 tunnel on my router with HurricaneElectric and now my #ipv6 works fine. So I'm going to go ahead and assume this is a problem at #XMission and not specifically the router.

Tunnel doesn't have a lot of bandwidth though, so probably going to be very temporary.

Der #Vodafone Support hat auf meine Frage nach #IPv6 irgendwas mit Dual Stack gemurmelt, also nehme ich mal an, dass er das inhaltlich verstanden hat. Das soll nun im Lauf des Tages aktiviert werden. Muss ich jetzt auf Verdacht die Fritze rebooten oder so? Aktuell ist ein #6in4-Tunnel konfiguriert.