|
Ticket ID: SIXXS #870208 Ticket Status: Resolved PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)
Routed subnet not working through tunnel
![[us]](/s/countries/us.gif) Shadow Hawkins on Wednesday, 03 December 2008 15:39:04
Username:AL4315-RIPE
Email:ripe@clusterfsck.com
The routed subnet (2001:4978:15b::/48) associated with my tunnel (T14780) doesn't seem to be working. My gateway box can send IPv6 traffic using its tunnel endpoint address, but addresses sourced from the subnet range aren't accepted. Everything was working fine a couple of days ago. Tried restarting aiccu, but no change.
I'm using a heartbeat tunnel. Gateway is Debian Linux 2.6.24 running aiccu. Aiccu reports no problems (it doesn't check subnet).
shinjuku is the name of my gateway box.
2001:4978:f:e6::2 is IPv6 address of my side of the tunnel
2001:4978:15b:1::1 is IPv6 address of gateway in the routed subnet
shinjuku:~# ping6 -c 5 -n -I 2001:4978:f:e6::2 www.kame.net
PING www.kame.net(2001:200:0:8002:203:47ff:fea5:3085) from 2001:4978:f:e6::2 : 56 data bytes
64 bytes from 2001:200:0:8002:203:47ff:fea5:3085: icmp_seq=1 ttl=53 time=221 ms
64 bytes from 2001:200:0:8002:203:47ff:fea5:3085: icmp_seq=2 ttl=53 time=222 ms
64 bytes from 2001:200:0:8002:203:47ff:fea5:3085: icmp_seq=3 ttl=53 time=222 ms
64 bytes from 2001:200:0:8002:203:47ff:fea5:3085: icmp_seq=4 ttl=53 time=222 ms
64 bytes from 2001:200:0:8002:203:47ff:fea5:3085: icmp_seq=5 ttl=53 time=222 ms
--- www.kame.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 221.261/222.341/222.653/0.685 ms
shinjuku:~# ping6 -c 5 -n -I 2001:4978:15b:1::1 www.kame.net
PING www.kame.net(2001:200:0:8002:203:47ff:fea5:3085) from 2001:4978:15b:1::1 : 56 data bytes
--- www.kame.net ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms
shinjuku:~#
Any info. or help resolving this issue is greatly appreciated. Thanks!!!!
-Arion
State change: resolved
The state of this ticket has been changed to resolved
Routed subnet not working through tunnel
Some strange sync issue on the PoP, has been resolved.
Routed subnet not working through tunnel
Shadow Hawkins on Wednesday, 18 February 2009 11:10:56
I think I'm seeing this problem again, I can ping6 to my external server and from there I see the echo request, echo reply, and it gets destination unreachable from unassigned.v6.your.org:
02:04:43.298519 IP6 2001:4978:138:0:223:54ff:fe6e:278b > 2001:470:1:41:a800:ff:fe53:3173: ICMP6, echo request, seq 1, length 64
02:04:43.298549 IP6 2001:470:1:41:a800:ff:fe53:3173 > 2001:4978:138:0:223:54ff:fe6e:278b: ICMP6, echo reply, seq 1, length 64
02:04:43.364467 IP6 2001:4978:1:400:202:b3ff:feb4:5974 > 2001:470:1:41:a800:ff:fe53:3173: ICMP6, destination unreachable[|icmp6]
My subnet here is 2001:4978:138::/48 and the tunnel is T13830 running on an openwrt kamikaze 7.09 running aiccu 2007.01.15-console. This happened a week or two ago also. Thanks.
Routed subnet not working through tunnel
Can you please provide the details from the "Reporting Problems" section?
Routed subnet not working through tunnel
Shadow Hawkins on Wednesday, 18 February 2009 13:06:57
It has started working again, do you still want more details? I have a pcap file from my remote server too showing the icmp messages above if that would be helpful.
Routed subnet not working through tunnel
What would you sending traffic to point B somewhere far away show?
Routed subnet not working through tunnel
Shadow Hawkins on Wednesday, 18 February 2009 13:15:34
Well the tunnel works anyway, I could connect from the router to anything all along. If I would connect outward from the subnet to my server I could see that the connection was getting through but the reply from the server back to the client in the subnet was getting the destination unreachable message.
Routed subnet not working through tunnel
Shadow Hawkins on Wednesday, 18 February 2009 13:12:00
Here is a traceroute to the pop on ipv4:
traceroute to uschi02.sixxs.net (216.14.98.22), 30 hops max, 38 byte packets
1 c-24-2-50-1.hsd1.ca.comcast.net (24.2.50.1) 6.826 ms 7.569 ms 7.491 ms
2 ge-2-1-sr01.davis.ca.sacra.comcast.net (68.87.213.57) 7.418 ms 5.958 ms 7.229 ms
3 te-9-1-ar01.sacramento.ca.sacra.comcast.net (68.87.212.25) 8.040 ms 10.283 ms 7.831 ms
4 be-60-ar01.oakland.ca.sfba.comcast.net (68.86.143.25) 11.459 ms 9.972 ms 21.136 ms
5 pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.90.141) 13.587 ms 13.101 ms 14.449 ms
6 pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.78) 16.918 ms 18.142 ms 17.507 ms
7 Tenge13-3.br02.sjo01.pccwbtn.net (63.218.179.25) 20.122 ms 19.328 ms 20.521 ms
8 your.org.ge2-5.br02.chc01.pccwbtn.net (63.218.5.38) 79.403 ms 79.152 ms 79.291 ms
9 sixxs.cx01.chi.bb.your.org (216.14.98.22) 77.638 ms 77.409 ms 97.397 ms
Routed subnet not working through tunnel
Shadow Hawkins on Thursday, 19 February 2009 15:04:19
I am having this exact same problem on the same POP: the tunnel endpoint has full connectivity via its endpoint address, but the subnet is not being routed.
Tracing out from one of my machines:
[nwhitehorn@trantor ~]$ traceroute6 -n www.ipv6.org
traceroute6 to shake.stacken.kth.se (2001:6b0:1:ea:202:a5ff:fecd:13a6) from 2001:4978:137:1:2e0:81ff:fe62:52b1, 64 hops max, 12 byte packets
1 2001:4978:137:1::1 0.591 ms 0.392 ms 0.370 ms
2 * * *
3 * * *
Packets are being routed through my gateway (2001:4978:137:1::1) onto the tunnel and then being dropped silently.
From a remote host to the internal interface on the gateway:
[nwhitehorn@freefall ~]$ traceroute6 cepheid.tachypleus.net
traceroute6 to cepheid.tachypleus.net (2001:4978:137:1::1) from 2001:4f8:fff6::28, 64 hops max, 12 byte packets
1 ipv6gw 0.279 ms 0.361 ms 0.261 ms
2 freebsd.r7.pao1.isc.org 1.581 ms 1.404 ms 1.465 ms
3 gig-2-0-0.r1.pao1.isc.org 1.534 ms 1.245 ms 1.297 ms
4 paix.ipv6.he.net 1.289 ms 1.411 ms 1.733 ms
5 10gigabitethernet4-1.core1.sjc2.he.net 2.898 ms 2.136 ms 2.320 ms
6 10gigabitethernet1-1.core1.chi1.he.net 65.064 ms 59.915 ms 64.042 ms
7 2001:470:0:7f::2 60.096 ms 60.225 ms 60.067 ms
8 unassigned.v6.your.org 66.950 ms 67.209 ms 67.415 ms
9 unassigned.v6.your.org 67.008 ms !A 67.223 ms !A 67.252 ms !A
The last two with a numeric trace:
8 2001:4978:1:400:202:b3ff:feb4:5974 67.102 ms 68.281 ms 67.690 ms
9 2001:4978:1:400:202:b3ff:feb4:5974 66.995 ms !A 67.099 ms !A 68.419 ms !A
The POP is returning all packets for the subnet marked destination unreachable.
whereas, asking for the tunnel endpoint address:
[nwhitehorn@freefall ~]$ traceroute6 2001:4978:f:98::2
traceroute6 to 2001:4978:f:98::2 (2001:4978:f:98::2) from 2001:4f8:fff6::28, 64 hops max, 12 byte packets
1 ipv6gw 0.493 ms 0.316 ms 0.260 ms
2 freebsd.r7.pao1.isc.org 1.431 ms 1.416 ms 1.432 ms
3 gig-2-0-0.r1.pao1.isc.org 1.440 ms 1.266 ms 1.297 ms
4 paix.ipv6.he.net 3.929 ms 1.565 ms 1.298 ms
5 10gigabitethernet4-1.core1.sjc2.he.net 12.261 ms 2.141 ms 2.346 ms
6 10gigabitethernet1-1.core1.chi1.he.net 59.915 ms 70.729 ms 60.023 ms
7 2001:470:0:7f::2 60.515 ms 60.174 ms 60.315 ms
8 unassigned.v6.your.org 67.200 ms 67.123 ms 67.018 ms
9 cl-153.chi-02.us.sixxs.net 76.448 ms 76.346 ms 76.066 ms
In this case, the connection works perfectly and the gateway machine itself has full IPv6 access. The tunnel is a heartbeat tunnel.
Routed subnet not working through tunnel
Shadow Hawkins on Saturday, 21 February 2009 17:59:58
I've had the same thing recently with my T14292 tunnel and R8009 subnet. Pings from the subnet would make it out, but the responses would get network unavailable from the uschi02 PoP, as observed using tcpdump on the ping target. Unfortunately, the tunnel seems to be having more serious problems at the moment so I can't get the data for a proper report.
Routed subnet not working through tunnel
Shadow Hawkins on Saturday, 21 February 2009 18:34:14
It is working for me at the moment.
Routed subnet not working through tunnel
Shadow Hawkins on Monday, 23 February 2009 20:25:53
I started working again for me this weekend, but has now quit with the exact same symptoms as before. Maybe some routing table problem on the POP?
Routed subnet not working through tunnel
Shadow Hawkins on Saturday, 07 March 2009 21:03:46
Packet routing to my subnet (2001:4978:137::/48) has been failing at regular intervals every few days now. It is dead now, for instance, though packets going directly to the tunnel endpoint continue to arrive without any problems. I suppose this problem might be fixed by the upcoming server move, but it would be nice if someone could take a look. Thanks!
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 03 December 2008 15:59:11
Posting is only allowed when you are