Subj : nlede01 down
To   : Benny Pedersen
From : Michiel van der Vlist
Date : Thu Jul 21 2011 22:31:34


Hello Benny,

On Thursday July 21 2011 10:26, you wrote to me:

 MvdV>> It was my SixXs tunnel that was down. 2001:7bf:2ff:3a9::2.

 BP> okay did not know you had more then one tunnel brokker, sixxs seems
 BP> stable enough if i have static ipv4 and allways on here, on dynamic
 BP> ipv4 sixxs have issues :(

I have a quasi static IP. That is, it is dynamic in theory, but it never changes as long as I do not change MAC address.

But SixXs has more than one problem and not all of them are technical. :-(


I started out with a SixXs AYIYA tunnel. The idea was to end the tunnel at my Fido machine because that would be online 24/7. That machine should also route the subnet for other machines on the LAN.

But that doesn't work. The procedure described in the SixXs faq does not work for AYIYA tunnels in combination with windows. When I reported that, Jeroen Massar told me, it was a known problem and it was reported in the "known problems" section. When i asked him why the FAQ was not updated, I got some snotty response, suggesting it was all my own fault that I had not read ALL of re documentation...

That pissed me off.

So I got the old linksys flashed with DD-WRT, requested a tunnel with he.net and let the linksys end the tunnel and route the subnet. THAT worked.

 BP> are you btw testing multiisp ipv6 failover / loadbalance ?

No, I haven't gotten around to that. First I have to find a way to change the priorities. The SixXs tunnel seems to have priority over the he.net tunnel. I wish it were the other way around because the he.net tunnel is more stable and faster than the sixXs tunnel.

 BP> actuly you now have 3 isps :)

Yes, one for IPv4 and two for IPv6. ;-)


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20070503
 * Origin: 2001:470:1f15:1117::1 (2:280/5555)

.