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
Insecure Implementation of Tunneling Protocols (GRE/IPIP/4in6/6in4) - Researchers at the DistriNet-KU Leuven research group have discovered millions of vulnerable Internet systems that accept unauthenticated IPIP, GRE, 4in6, or 6in4 traffic. This can be considered a generalization of the vulnerability in VU#636397
@leeloo Until regulators like @BNetzA get their shit together and mandate a /64 of #IPv6 to be supplied to every #internet connection with no exceptioms or charges and mandates services and devices to support it as well, we'll not he above to get rid of #IPv4.
Meanwhile it would be cheaper and easier for me to literally get my own private /24 of IPv4s than to convince my ISP to offer me even a single /48 of IPv6s...
Unfortunately, my #6in4 tunnel from #HE's #tunnelbroker keeps underperforming a bit today (still see occassional packet loss as well), after being really bad yesterday ...
Going v6-only makes no difference here because all my hosts were already configured to *prefer* v6.
Maybe I'll recheck the native #IPv6 offered by my ISP whether I can finally have a prefix larger than /64 ... if so, I might go for "multi-homed", preferring the native v6 for outgoing traffic...
@dantheclamman @jeroen @huitema wasn't #Teredo Microsoft's #6in4 #tunneling protocol that also does #NAT-puncturing?
Litchralee_v6
Paradox
j.r / Julian
D_70WN 🌈 🏳️⚧️
Kevin Karhan 
Felix Palmen 
jzdm
Sami Lehtinen
Ryan Littlefield