SixXS::Sunset 2017-06-06

Routing problem in amis.net?
[pl] Carmen Sandiego on Monday, 07 September 2009 23:56:21
Hi! I have a 6to4 at my home and sixxs at work. My sixxs IP is 2001:15c0:65ff:d2::2 My home IP is 2002:d999:566e::2171:5308:6110 The problem is that I cannot connect between them although connection to other IPv6 sites seems to be OK from both sites! The traceroute from both sides seems to stop in the very same place: # traceroute6 2002:d999:566e::2171:5308:6110 traceroute to 2002:d999:566e::2171:5308:6110 (2002:d999:566e::2171:5308:6110) from 2001:15c0:65ff:d2::2, 30 hops max, 16 byte packets 1 gw-211.mbx-01.si.sixxs.net (2001:15c0:65ff:d2::1) 43.164 ms 37.343 ms 42.109 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 42.824 ms 45.515 ms 46.947 ms 3 * * * and: # traceroute6 2001:15c0:65ff:d2::2 traceroute to 2001:15c0:65ff:d2::2 (2001:15c0:65ff:d2::2) from 2002:d999:566e::2171:5308:6110, 30 hops max, 16 byte packets 1 2002:c058:6301:: (2002:c058:6301::) 2.34 ms 2.123 ms 2.165 ms 2 sl-bb1v6-bru-t-34.sprintv6.net (2001:440:eeee:ffb5::1) 38.001 ms 37.93 ms 38.011 ms 3 2001:440:eeee:ffe7::2 (2001:440:eeee:ffe7::2) 50.223 ms 49.971 ms 50.725 ms 4 amis-polaris.v6.telekom.at (2001:890:600:8002::8591) 43.424 ms 46.09 ms 49.078 ms 5 maribor3-te-1-3.amis.net (2001:15c0:ffff:d::5) 47.043 ms 47.976 ms 52.348 ms 6 * * * Is there some problem at maribor3.amis.net? Is anyone else experiencing similar problems?
Routing problem in amis.net?
[si] Shadow Hawkins on Wednesday, 09 September 2009 18:45:11
Hi! I have a tunnel from the Amis POP and if I traceroute your ***:6110 address it also stops at the second hop, just as for you. For other hosts, like ipv6.google.com, it goes thru nicely. Hope this info helps you further... David
Routing problem in amis.net?
[pl] Carmen Sandiego on Thursday, 10 September 2009 11:27:23
The ::6110 is my SixXS IP so the problem is not related to 6to4. Do you know any contact address for Amis to report the problem?
Routing problem in amis.net?
[ch] Jeroen Massar SixXS Staff on Thursday, 10 September 2009 11:32:24
2002:d999:566e::2171:5308:6110 = 6to4 (2002::/16) of which the IPv4 is 217.153.86.110. 6to4 has nothing to do with SixXS and we recommend people to steer away from it as one cannot debug it....
Routing problem in amis.net?
[pl] Carmen Sandiego on Thursday, 10 September 2009 17:11:11
You are right. I have pasted the wrong address. Effectively I can debug 6to4 as I know who operates the router I'm using as the other side of the tunnel. However the problem lays further deep in the IPv6 Internet. Alternatively I can request for more tunnels but I don't wont to utilize more 'neverending' IPv6 ranges than I need without good purpose.
Routing problem in amis.net?
[ch] Jeroen Massar SixXS Staff on Thursday, 10 September 2009 18:23:54
Effectively I can debug 6to4 as I know who operates the router
I'm using as the other side of the tunnel.
Knowing the other side doesn't matter, it is the intermediate hops in both IPv4 and IPv6 that count.
Alternatively I can request for more tunnels but I don't wont
to utilize more 'neverending' IPv6 ranges than I need without good purpose.
We suggest that everybody: - get a tunnel when you want to make a single host IPv6 connected. - get a tunnel+subnet when you want a host + network IPv6 connected. The option for multiple tunnels&subnets is there, just have enough credits.
Routing problem in amis.net?
[pl] Carmen Sandiego on Thursday, 10 September 2009 19:08:42
You are right. The routing back to 6to4 might be faulty and in general hard to debug. I'll do what you suggested. I have about 600 credits so it won't be a problem. Thank you for you explanations. Best regards.
Routing problem in amis.net?
[ch] Jeroen Massar SixXS Staff on Wednesday, 09 September 2009 23:09:01
6to4 issues can exist anywhere on both the IPv4 and the IPv6 layer. As debugging is because of that extremely difficult I can only suggest to not use it, unless you have control over/ability to check both all IPv4 nodes involved and all IPv6 nodes involved. Generally 6to4 also causes very scenic routing. FYI: I cannot reach 2002:d999:566e::2171:5308:6110 either when trying to traceroute from other locations.

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

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