SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #5435186
Ticket Status: Resolved

PoP: deham01 - Easynet (Hamburg)

Subnet R8373 no longer routed
[de] Carmen Sandiego on Thursday, 25 August 2011 10:01:02
Dear Sixxs people, my Name is Andreas Hassfeld and my NIC Handle is AH70-6BONE. I have an additional subnet R8373 routed over tunnel T19696. The tunnel IPs are still working, but the subnet seems to be no longer routed. I tried to reach the net from an external host, wich has also a tunnel to Sixxs, have a look: I'm pinging your IPv6 of the transport tunnel:
ahassfeld@dl1:~$ ping6 -n 2001:6f8:900:c51::1 PING 2001:6f8:900:c51::1(2001:6f8:900:c51::1) 56 data bytes 64 bytes from 2001:6f8:900:c51::1: icmp_seq=1 ttl=64 time=15.7 ms 64 bytes from 2001:6f8:900:c51::1: icmp_seq=2 ttl=64 time=16.1 ms 64 bytes from 2001:6f8:900:c51::1: icmp_seq=3 ttl=64 time=17.1 ms 64 bytes from 2001:6f8:900:c51::1: icmp_seq=4 ttl=64 time=16.6 ms --- 2001:6f8:900:c51::1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3002ms rtt min/avg/max/mdev = 15.787/16.448/17.139/0.523 ms
I'm pinging my end of the tunnel, works also:
ahassfeld@dl1:~$ ping6 -n 2001:6f8:900:c51::2 PING 2001:6f8:900:c51::2(2001:6f8:900:c51::2) 56 data bytes 64 bytes from 2001:6f8:900:c51::2: icmp_seq=1 ttl=63 time=66.3 ms 64 bytes from 2001:6f8:900:c51::2: icmp_seq=2 ttl=63 time=66.9 ms 64 bytes from 2001:6f8:900:c51::2: icmp_seq=3 ttl=63 time=65.7 ms 64 bytes from 2001:6f8:900:c51::2: icmp_seq=4 ttl=63 time=65.8 ms --- 2001:6f8:900:c51::2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 65.797/66.246/66.974/0.546 ms
But when I try to ping an IP on the subnet, your router does not forward them:
ahassfeld@dl1:~$ ping6 -n 2001:6f8:11f3:7::1 PING 2001:6f8:11f3:7::1(2001:6f8:11f3:7::1) 56 data bytes From 2001:6f8:900:693::1 icmp_seq=1 Destination unreachable: No route From 2001:6f8:900:693::1 icmp_seq=2 Destination unreachable: No route From 2001:6f8:900:693::1 icmp_seq=3 Destination unreachable: No route From 2001:6f8:900:693::1 icmp_seq=4 Destination unreachable: No route From 2001:6f8:900:693::1 icmp_seq=5 Destination unreachable: No route From 2001:6f8:900:693::1 icmp_seq=6 Destination unreachable: No route --- 2001:6f8:11f3:7::1 ping statistics --- 6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5000ms
I've tried traceroute to confirm that not my endpoint is bouncing the packets, but deham01 is:
ahassfeld@dl1:~$ traceroute6 2001:6f8:11f3:7::1 traceroute to 2001:6f8:11f3:7::1 (2001:6f8:11f3:7::1) from 2001:6f8:900:693::2, 30 hops max, 24 byte packets 1 gw-1684.ham-01.de.sixxs.net (2001:6f8:900:693::1) 18.43 ms !N 17.963 ms !N 17.974 ms !N
This is the external source IP I've used, this tunnel goes to deham01, as well as the target tunnel.
ahassfeld@dl1:~$ ifconfig sixxs sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:6f8:900:693::2/64 Scope:Global inet6 addr: fe80::53f6:53de/128 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:152752 errors:0 dropped:0 overruns:0 frame:0 TX packets:152752 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15886544 (15.1 MB) TX bytes:18941152 (18.0 MB)
I've tried disabling and enabling the tunnel and the subnet, but the problem persists. Could you have a look, please? Yours, Andreas
Subnet R8373 no longer routed
[de] Carmen Sandiego on Monday, 29 August 2011 11:13:52
Update: Tunnel is routed again, it seems to work right now. Yours, Andreas
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 02 September 2011 14:01:51
Message is Locked
The state of this ticket has been changed to resolved

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

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