|
Subnet Routing?
![[us]](/s/countries/us.gif) Carmen Sandiego on Wednesday, 02 August 2006 03:47:42
My AYIYA tunnel remote endpoint is pingable as are other remote IPv6 addresses, but I am unable to ping these same addresses from subnet addresses associated with the tunnel.
An Ethereal packet capture shows ICMP Echo Requests being sent through the tunnel to remote IPv6 addresses, however ICMP Echo Replies are returned only if they originate from the local tunnel endpoint. All ICMP Echo Requests originating from the allocated subnet addresses never receive replies. My simple analysis is that the subnet is not being routed correctly at the PoP.
The configuration and tests are outlined below.
Any advice would be appreciated. TIA.
CONFIGURATION
System Alpha runs Windows XP SP2, has a single ethernet network adapter, is behind a NAT, and uses AICCU to create a virtual adapter (SixXS) and an AYIYA tunnel ...
local endpoint ==> 2001:4830:1600:16::2
remote endppoint ==> 2001:4830:1600:16::1
The tunnel is enabled, and the SixXS virtual network adapter is configured to forward packets.
Subnet 2001:4830:1619::/48 is allocated to the tunnel, and is enabled. The ethernet adapter is configured with address 2001:4830:1619::1, and is configured to forward and advertise. The routing table is ...
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- ---- ------------------------ --- ---------------------
yes Manual 0 2001:4830:1619::/64 5 Private
no Manual 0 2001:4830:1600:16::/64 4 SixXS
yes Manual 0 ::/0 4 2001:4830:1600:16::1
Systems Beta, Gamma, Delta, et al on same subnet are automatically configured with 2001:4830:1619::/48 addresses and a default route pointing to Alpha's link-local address.
TESTS
The local endpoint is pingable ...
Pinging 2001:4830:1600:16::2 from 2001:4830:1600:16::2 with 32 bytes of data:
Reply from 2001:4830:1600:16::2: time<1ms
Reply from 2001:4830:1600:16::2: time<1ms
Reply from 2001:4830:1600:16::2: time<1ms
Reply from 2001:4830:1600:16::2: time<1ms
Ping statistics for 2001:4830:1600:16::2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The remote endpoint is pingable ...
Pinging 2001:4830:1600:16::1 from 2001:4830:1600:16::2 with 32 bytes of data:
Reply from 2001:4830:1600:16::1: time=48ms
Reply from 2001:4830:1600:16::1: time=50ms
Reply from 2001:4830:1600:16::1: time=44ms
Reply from 2001:4830:1600:16::1: time=47ms
Ping statistics for 2001:4830:1600:16::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 50ms, Average = 47ms
noc.sixxs.net is pingable ...
Pinging noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] from 2001:4830:1600:16::
2 with 32 bytes of data:
Reply from 2001:838:1:1:210:dcff:fe20:7c7c: time=137ms
Reply from 2001:838:1:1:210:dcff:fe20:7c7c: time=188ms
Reply from 2001:838:1:1:210:dcff:fe20:7c7c: time=133ms
Reply from 2001:838:1:1:210:dcff:fe20:7c7c: time=240ms
Ping statistics for 2001:838:1:1:210:dcff:fe20:7c7c:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 240ms, Average = 174ms
noc.sixxs.net is NOT pingable from the subnet address assigned to the ethernet adapter (2001:4830:1619::1), i.e., ping -S 2001:4830:1619::1 noc.sixxs.net ...
Pinging noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] from 2001:4830:1619::1 w
ith 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:838:1:1:210:dcff:fe20:7c7c:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
noc.sixxs.net is NOT pingable from other systems (Beta, Gamma, Delta, et al) on the same subnet, i.e., 2001:4830:1619::/48.
Subnet Routing?
Shadow Hawkins on Wednesday, 02 August 2006 19:12:43
To find out exactly where the problem is the best thing would be to run a traceroute from a remote computer like the one available here:
http://www.berkom.blazing.de/tools/traceroute.cgi
Subnet Routing?
Ever tried looking in the misc section? It contains a Traceroute from all the SixXS PoPs, thus also from the host one is connected to.
Subnet Routing?
Carmen Sandiego on Thursday, 03 August 2006 19:38:12
I can traceroute to the tunnel endpoint at the PoP and to the tunnel endpoint in my system, but the traceroute appears to fail when trying to reach a subnet address associated with this tunnel and assigned to an adapter in my tunnel endpoint system. Here are the traceroutes from SixXS' Distributed Traceroute tool ...
IPv6 traceroute from usewr01.sixxs.net @ OCCAID Inc., AS30071 to 2001:4830:1600::1 (the tunnel endpoint at the PoP):
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
1. 2001:4830:e2:29::1 0.0% 5 0.6 0.7 0.6 0.8 0.1 30071 TowardEX Technologies Network
0.ge0-3.cr1.ewr1.us.occaid.net.
2. 2001:4830:ff:f150::2 0.0% 5 6.3 6.3 6.2 6.4 0.1 30071 TowardEX Technologies Network
ge-0-1-0.cr1.iad1.us.occaid.net.
3. 2001:504:0:2:0:3:3437:1 0.0% 5 6.5 6.5 6.4 6.5 0.1 EQUINIX-IX-V6
4. 2001:4830:1600::1 0.0% 5 6.8 6.7 6.6 6.8 0.1 30071 OCCAID Inc.
gw-1.qas-01.us.sixxs.net.
IPv6 traceroute from usewr01.sixxs.net @ OCCAID Inc., AS30071 to 2001:4830:1600::2 (the tunnel endpoint at my system):
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
1. 2001:4830:e2:29::1 0.0% 5 0.7 0.7 0.5 0.8 0.1 30071 TowardEX Technologies Network
0.ge0-3.cr1.ewr1.us.occaid.net.
2. 2001:4830:ff:f150::2 0.0% 5 6.2 6.3 6.2 6.4 0.1 30071 TowardEX Technologies Network
ge-0-1-0.cr1.iad1.us.occaid.net.
3. 2001:504:0:2:0:3:3437:1 0.0% 5 6.5 6.5 6.4 6.8 0.2 EQUINIX-IX-V6
4. 2001:4830:e6:7::2 0.0% 5 6.8 6.8 6.7 7.1 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
5. 2001:4830:1600::2 0.0% 5 21.3 21.1 20.8 21.3 0.2 30071 OCCAID Inc.
cl-1.qas-01.us.sixxs.net.
IPv6 traceroute from usewr01.sixxs.net @ OCCAID Inc., AS30071 to 2001:4830:1619::1 (an subnet address assigned to this tunnel, and configured on an adapter in the my tunnel endpoint system):
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
1. 2001:4830:e2:29::1 0.0% 5 0.7 0.7 0.5 0.8 0.1 30071 TowardEX Technologies Network
0.ge0-3.cr1.ewr1.us.occaid.net.
2. 2001:4830:ff:f150::2 0.0% 5 6.3 6.3 6.2 6.3 0.1 30071 TowardEX Technologies Network
ge-0-1-0.cr1.iad1.us.occaid.net.
3. 2001:504:0:2:0:3:3437:1 0.0% 5 6.5 6.4 6.4 6.5 0.1 EQUINIX-IX-V6
4. 2001:4830:e6:7::2 0.0% 5 6.6 6.7 6.6 6.8 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
5. 2001:4830:e6:7::2 0.0% 5 6.8 6.7 6.6 6.8 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
6. 2001:4830:e6:7::2 0.0% 5 6.7 6.8 6.6 7.2 0.3 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
7. 2001:4830:e6:7::2 0.0% 5 6.9 6.7 6.7 6.9 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
8. 2001:4830:e6:7::2 0.0% 5 6.7 6.7 6.6 7.0 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
9. 2001:4830:e6:7::2 0.0% 5 7.1 6.8 6.6 7.1 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
10. 2001:4830:e6:7::2 0.0% 5 6.6 6.7 6.6 6.8 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
11. 2001:4830:e6:7::2 0.0% 5 6.9 6.8 6.6 7.2 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
12. 2001:4830:e6:7::2 0.0% 5 6.6 6.7 6.6 6.8 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
13. 2001:4830:e6:7::2 0.0% 5 6.8 7.0 6.8 7.2 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
14. 2001:4830:e6:7::2 0.0% 5 6.8 6.7 6.6 6.8 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
15. 2001:4830:e6:7::2 0.0% 5 6.6 6.7 6.5 7.0 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
16. 2001:4830:e6:7::2 0.0% 5 7.1 6.8 6.6 7.1 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
17. 2001:4830:e6:7::2 0.0% 5 6.9 6.8 6.6 7.0 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
18. 2001:4830:e6:7::2 0.0% 5 6.8 6.8 6.7 6.9 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
19. 2001:4830:e6:7::2 0.0% 5 6.9 6.8 6.6 6.9 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
20. 2001:4830:e6:7::2 0.0% 5 7.2 6.8 6.6 7.2 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
21. 2001:4830:e6:7::2 0.0% 5 7.1 6.7 6.5 7.1 0.3 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
22. 2001:4830:e6:7::2 0.0% 5 6.6 6.8 6.6 7.3 0.3 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
23. 2001:4830:e6:7::2 0.0% 5 6.9 6.8 6.6 7.0 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
24. 2001:4830:e6:7::2 0.0% 5 6.9 6.7 6.6 6.9 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
25. 2001:4830:e6:7::2 0.0% 5 7.1 6.8 6.6 7.1 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
26. 2001:4830:e6:7::2 0.0% 5 6.8 6.7 6.5 7.1 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
27. 2001:4830:e6:7::2 0.0% 5 7.0 6.7 6.5 7.0 0.2 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
28. 2001:4830:e6:7::2 0.0% 5 6.7 6.7 6.5 6.8 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
29. 2001:4830:e6:7::2 0.0% 5 6.8 6.8 6.5 6.9 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
30. 2001:4830:e6:7::2 0.0% 5 7.0 6.8 6.6 7.0 0.1 30071 TowardEX Technologies Network
sixxs-asbnva-gw.customer.occaid.net.
Subnet Routing?
Shadow Hawkins on Friday, 04 August 2006 04:37:16
Okay, this looks a lot like the problem I had when I first setup my subnet. In the end I just disabled the subnet, then reenabled it. Then about 15 minutes later it was all working properly.
Subnet Routing?
Carmen Sandiego on Saturday, 05 August 2006 01:06:37
I appreciate the advice.
I tried enabling and disabling the subnet, but the subnet still doesn't work as expected. I am unable to ping from the subnet's addresses to public IPv6 addresses, nor are public IPv6 ping and traceroute tools able to reach the subnet's addresses.
I've reported the problem to the SixXS Staff at the contact address.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 03 August 2006 09:52:23
Posting is only allowed when you are