IPv6 with Hurricane Electric Tunnel Broker - Documentation out of date

SIGUSRpi

On top of that if you have only your normal IPv4 WAN connection and an IPv6 tunnel from HE (why would you even consider using another IPv6 connection in addition to your HE tunnel?)

I'm not the person you were replying to, but speaking for myself, I see things like this on my HE tunnel all the time:

Feb 12 14:00:45 	dpinger 		OPT3V6_TUNNELV6 2001:470:7:117e::1: Alarm latency 33734us stddev 19534us loss 21%
Feb 12 14:00:58 	dpinger 		OPT3V6_TUNNELV6 2001:470:7:117e::1: Clear latency 33166us stddev 19392us loss 20%
Feb 13 10:51:11 	dpinger 		OPT3V6_TUNNELV6 2001:470:7:117e::1: Alarm latency 28309us stddev 9549us loss 22%
Feb 13 10:51:12 	dpinger 		OPT3V6_TUNNELV6 2001:470:7:117e::1: Alarm latency 605795us stddev 2656495us loss 19%
Feb 13 10:52:07 	dpinger 		OPT3V6_TUNNELV6 2001:470:7:117e::1: Alarm latency 137034us stddev 756717us loss 12%
Feb 13 10:52:11 	dpinger 		OPT3V6_TUNNELV6 2001:470:7:117e::1: Clear latency 33363us stddev 17753us loss 7%

My homelab setup is much simpler than pbnet's, in that right now it's just one IPv4 through my ISP, and one IPv6 tunnel via HE. But due to the regular latency spikes, I'm considering trying to figure out how to set up some kind of multi-WAN thing, using my ISP's own IPv6 as the other uplink. The issue is that my ISP's IPv6 is hilariously terrible, so I need to keep HE's tunnel as an option. I think multi-WAN connections like this should be able to either failover or load-balance when the latency gets high enough to set off alarms, it's just I haven't had the time and energy to make the attempt.

So anyhow, that's just one example of why somebody might need a connection in addition to the tunnel.