Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by wRAR, June 07, 2012, 09:54:45 AM
Quote from: kasperd on June 08, 2012, 02:40:54 AMThroughput should not drop that much just because of increased latency. I can't help wondering if the test you are using is skewing things by being more sensitive to latency on the IPv6 connection than it is on the IPv4 connection. Of course it is of course also possible that you are running into a congested link and dropping packets.
Quote from: kasperd on June 08, 2012, 02:40:54 AMRemember, you can create another tunnel without deleting the current one
Quote from: wRAR on June 08, 2012, 06:45:38 AMWrong: "You already have a tunnel to this IP.".
Quote from: cholzhauer on June 07, 2012, 09:55:48 AMTunneled IPv6 should be slower than IPv4 in most cases, but yours may be a little extreme
Quote from: cholzhauer on June 11, 2012, 09:11:36 AMExcept that the HE tunnel always works, even if it is slow
Quote from: wRAR on June 11, 2012, 08:59:10 AMStockholm (79 ms ping):Frankfurt (89 ms ping):As in 2 years of using he.net tunnels I didn't find any practical advantages of that (apart from greatly increased time of apt-get dist-upgrade), the solution is obvious.
Quote from: mleber on June 11, 2012, 11:16:04 PMPick a provider that has an upstream that IPv4 peers with Hurricane, if not native IPv6 peering so that you can get native IPv6?
Quote from: mleber on June 11, 2012, 11:16:04 PMI'm assuming you picked them because they are actually the closest you could pick.
Quote from: mleber on June 11, 2012, 11:16:04 PMAnd now, due to happy eyeballs being included in modern browsers, you can even leave it on all the time and whichever address family (IPv6 or IPv4) is faster will be the one that is used.