SixXS::Sunset 2017-06-06

Issues connecting to sixxs.net from 6to4
[ca] Shadow Hawkins on Sunday, 21 March 2010 21:12:55
I have setup IPv6 on my network via an Apple Airport Extreme router, using the 'automatic' mode. The automatic mode is essentially a 6to4. If I try connecting to ipv6.google.com I have no issues when my computer is using the IPv6 address. On the other hand it is not the same story when I try connecting to sixxs.net or sixxs.org. Usually the connection will time out before I manage to get the web page displayed. The only way I can connect to the site is by disabling IPv6 look ups in Firefox or deactivating IPv6 on the computer. Looking at the settings for my wireless network interface on the computer, I see: router: fe80:0000:0000:0000:0225:00ff:fefe:3b5f address: 2002:4635:8b86:0000:0223:6cff:fe88:684f prefix length: 64 Can anyone suggest what the issue might be, since I don't want to have to go through these hoops to connect to this site? Note: I can't configure the Airport Extreme to use a Sixxs.net tunnel, due to a limitation in the Apple firmware.
Issues connecting to sixxs.net from 6to4
[ch] Jeroen Massar SixXS Staff on Monday, 22 March 2010 11:08:48
First of all, you are talking about 6to4, as such, even though next I will ask for a traceroute, it won't help much as packets might be pulled to the left and right and other unknown directions on both IPv4 and IPv6, both of which might be anycasted, thus debugging 6to4 is nearly impossible unless one would have access to every single hop along the route, which most very likely is not the case.
When I try connecting to sixxs.net or sixxs.org.
Which exact host are you trying to reach? www.sixxs.net and the IPv6gate too are hosted on a cluster of different servers at different ISPs, as such that might make it even more difficult to debug, but a traceroute to each might already help a bit.
Usually the connection will time out before I manage to get the web page
displayed.
That could quite well be an MTU issue. For 6to4 this is always 1280.
Can anyone suggest what the issue might be, since I don't want to have to go
through these hoops to connect to this site?
That looks more or less fine, nothing much one can state about those details. Other details are way more important though.
Note: I can't configure the Airport Extreme to use a Sixxs.net tunnel, due to
a limitation in the Apple firmware.
Can't do much about a closed box, as one can't even look inside it.... The only thing you could do, but might be far from ideal, is to use another host for terminating the tunnel and distribute a subnet from there.
Issues connecting to sixxs.net from 6to4
[no] Shadow Hawkins on Tuesday, 23 March 2010 15:11:42
Note: I can't configure the Airport Extreme to use a Sixxs.net tunnel, due to a limitation in the Apple firmware.
Out of curiosity; what limitation is that? Both my Extreme-boxes has options for a IPv6-over-IPv4 tunnel. I've never tested them though, but can't think of any reason it /shouldn't/ work.
Issues connecting to sixxs.net from 6to4
[ca] Shadow Hawkins on Wednesday, 24 March 2010 14:31:08
The issue is if you are connecting to your service provider via PPPoE the IPv6 tunnel won't work. It apparently works fine if you connect via DHCP. This essentially prevents most people using DSL for using the tunnel. The issue was confirmed as 'known' by an Apple engineer, when I filed a bug report with them. Until there is a confirmed fix, I am holding out on buying any newer versions of the Apple Airport Extreme, and even then this experience has left me disappointed in Apple's willingness to fix Airport bugs. I would look to the competition, but the competition is not generally IPv6 ready. BTW From what I can tell, by 6to4 is being handled by swip.net.
traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 52 byte packets 1 10.0.1.1 (10.0.1.1) 5.824 ms 0.638 ms 0.555 ms 2 bas7-montreal28_lo0_symp.net.bell.ca (64.230.197.166) 7.281 ms 7.683 ms 7.251 ms 3 dis23-montreal02_vlan134.net.bell.ca (64.230.172.225) 10.430 ms 6.078 ms 5.853 ms 4 core4-montreal02_gig12-3.net.bell.ca (64.230.170.129) 5.597 ms 6.165 ms 15.868 ms 5 ncore3-montreal02_pos0-8-0-0_core.net.bell.ca (64.230.168.221) 13.965 ms 15.065 ms 14.169 ms 6 newcore1-newyork83_so1-0-0.net.bell.ca (64.230.187.129) 13.313 ms 13.539 ms 12.894 ms 7 core1-newyork83_pos3-0-0_core.net.bell.ca (64.230.187.82) 13.092 ms 13.141 ms 13.110 ms 8 nyc9-core-2.gigabiteth0-2.swip.net (130.244.200.69) 13.708 ms 13.180 ms 13.105 ms 9 nyc9-core-1.pos11-0.swip.net (130.244.194.201) 12.985 ms 14.037 ms 13.878 ms 10 ams-core-1.pos0-7-4-0.swip.net (130.244.218.141) 89.401 ms 89.683 ms 90.028 ms 11 ams13-core-1.tengigabiteth2-4.swip.net (130.244.52.169) 88.697 ms * *
As to the IPv6 traceroute:
traceroute6 www.sixxs.net traceroute6: Warning: nginx.sixxs.net has multiple addresses; using 2001:7b8:3:4f:202:b3ff:fe46:bec traceroute6 to nginx.sixxs.net (2001:7b8:3:4f:202:b3ff:fe46:bec) from 2002:4635:8b86::223:6cff:fe88:684f, 64 hops max, 12 byte packets 1 2002:4635:8b86::225:ff:fefe:3b5f 0.886 ms 0.763 ms 0.678 ms 2 * * * 3 ams-core-1.tengige0-0-0-0.swip.net 114.735 ms 112.042 ms 112.369 ms 4 ams16-core-1.tengigabiteth2-0-0.tele2.net 190.971 ms 137.312 ms 112.871 ms 5 amsix-501.xe-0-0-0.jun1.kelvin.network.bit.nl 102.358 ms 101.981 ms 102.100 ms 6 nlede01.sixxs.net 102.740 ms 102.212 ms 102.826 ms
Issues connecting to sixxs.net from 6to4
[ch] Jeroen Massar SixXS Staff on Wednesday, 24 March 2010 14:54:06
10 ams-core-1.pos0-7-4-0.swip.net (130.244.218.141) 89.401 ms 89.683 ms 90.028 ms
11 ams13-core-1.tengigabiteth2-4.swip.net (130.244.52.169) 88.697 ms * *
You do realize that thus *ALL* your traffic is getting an extra 80ms slapped onto it and being sent to Amsterdam..... One of the many reasons to avoid 6to4 IMHO. If you had the possibility, get a little WRT box or a ALIX/WRAP/soekris or something like that and terminate a tunnel on that, will safe you a lot of headaches with Apple and your connectivity would be so much better.. Or, if you only use one host just terminate the tunnel on that one.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker