Subj : test-ipv6.com
To   : Bj”rn Felten
From : Michiel van der Vlist
Date : Fri May 13 2011 13:44:59

Hello Bj”rn,

On Friday May 13 2011 12:51, you wrote to Janis Kracht:

 BF> It seems to default to Go6 though, and I think it has only one end
 BF> server as of yet. Sixxs has end servers all around the world, I myself
 BF> uses the Swedish server hosted by the same ISP that hosts e.g.
 BF> Wikileaks and The Pirate Bay... :)

Wel... when it comes to comparing tunnel brokers: I have two tunnels, one from SixXs and one from Hurricane Electric.

The SixXs tunnels starts at bit.nl in Ede NL, the he.net tunnel starts in Amsterdam NL.

Ny first attempt at IPv6 was with a tunnel that could penetrate NAT. So I got an Ayiya tunnel from sixxs. I got that to work on a windows XP machine. But the tunnel closed down every two minutes if there was no activity. The ayiya hartbeat mechanism is supposed to keep it open through NAT, but it didn't. So I used a klugde and had the Windows task manager sent a ping through the tunnel very minute. That keeps it open for incoming, but I do not relly like it.

The I applied for a subnet and attempted to route the subnet. I followed the procedure in the FAQ to the letter, but I could not get it to work.

When I ask for help in the sixxs forum, Jeroen Massar told me that routing a subnet does not work with windows and an ayiya tunnel. Whe I asked him why that was not mentioned in the FAQ, he replied that is was in the FAQ, in the section "known problems".

That's like having an instruction book, explaining a certain procedure on page two and then on the last page saying: Oh, BTW, the procedure mentiones on page 2, does not work.

That put me off...

So, next step. I took down the wrt54gl that had been running for FON, reflashed it with an ipv6 capable version of DD-WRT. I applied for a static tunnel at hurrican electic. The tunnel comes with a /64 subnet and if you want you can have a /48 subnet on request.

I installed the tunnel on my router, did some wizardry to advertise and route the subnet and that was that. No need to install tunnel drivers on the indivudual systems on the LAN, all ipv6 capanel systems on the LAN automaticaly.

Plus that the he.net tunnel is faster. When I run the test at ipv6-test.net, the he.net tunnel is some 10% faster than the sixxs tunnel. 4.0 up, 2.98 down for sixxs and 4.5 down and 3.3 up for the he.net tunnel. Both averaged over 4 runs.

(my ipv4 speed is 22 down, 4 up)


Plus that he.net does not have that silly credit system. You just apply for a tunnel and you get it within minutes. And you don't get snotty answers when you ask them a question.

I am happy with my he.net tunnel.


Cheers, Michiel

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

.