SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #597889
Ticket Status: User

PoP: (not applicable)

Tunnel reported unreachable - but it is...
[fr] Shadow Hawkins on Saturday, 27 October 2007 11:08:08
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Nic-Handle : PRF1-SIXXS Os : Linux Fedora 7, [root@riri rol]# uname -a Linux riri.as2917.net 2.6.22.9-61.fc6 #1 SMP Thu Sep 27 17:45:57 EDT 2007 i686 i686 i386 GNU/Linux Routing table : [root@riri rol]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0 [root@riri rol]# netstat -rn -A inet6 Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface 2001:6f8:202:160::/64 :: U 256 1228 0 sixxs 2001:6f8:3f9::/48 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 sixxs ::/0 2001:6f8:202:160::1 UG 1024 84 0 sixxs ::1/128 :: U 0 309 1 lo 2001:6f8:202:160::/128 :: U 0 0 2 lo 2001:6f8:202:160::2/128 :: U 0 1314 1 lo 2001:6f8:3f9::/128 :: U 0 0 2 lo 2001:6f8:3f9::2/128 :: U 0 0 1 lo fe80::/128 :: U 0 0 2 lo fe80::c0a8:102/128 :: U 0 0 1 lo fe80::240:63ff:fec4:65e3/128 :: U 0 0 1 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs [root@riri rol]# traceroute6 2001:6f8:202:160::1 traceroute to 2001:6f8:202:160::1 (2001:6f8:202:160::1), 30 hops max, 40 byte packets 1 gw-353.bru-01.be.sixxs.net (2001:6f8:202:160::1) 71.536 ms 73.049 ms 73.948 ms [root@riri rol]# traceroute 212.100.184.146 traceroute to 212.100.184.146 (212.100.184.146), 30 hops max, 40 byte packets 1 192.168.1.254 (192.168.1.254) 0.947 ms 1.135 ms 1.831 ms 2 82.232.32.254 (82.232.32.254) 57.460 ms 58.332 ms 58.979 ms 3 * * * 4 * * * 5 th1-6k-2-po21.intf.routers.proxad.net (212.27.57.214) 73.935 ms * * 6 th1-4k-1-v900.intf.routers.proxad.net (212.27.58.78) 70.144 ms 56.842 ms 57.236 ms 7 easynet.FreeIX.net (213.228.3.226) 58.095 ms 58.984 ms 59.728 ms 8 v121.br0.cpnan.fr.easynet.net (194.116.219.1) 61.757 ms 62.567 ms 62.708 ms 9 er0.cpnan.fr.easynet.net (194.116.218.130) 63.851 ms 57.058 ms 57.502 ms 10 ge3-0-1-111.gr10.cpnan.fr.easynet.net (87.86.71.112) 57.870 ms 58.514 ms 57.209 ms 11 te0-0-0.gr10.gdbru.be.easynet.net (87.86.77.47) 69.468 ms 70.355 ms 70.633 ms 12 87.86.71.165 (87.86.71.165) 81.980 ms 81.474 ms 80.290 ms 13 fe0-0.ar1.gdbru.be.easynet.net (212.100.191.8) 70.712 ms 70.783 ms 69.842 ms 14 bebru01.sixxs.net (212.100.184.146) 70.903 ms 71.377 ms 72.081 ms Description : you have notified me my tunnel is down, and the credits section is showing that you have removed me 5 points twice in a row because of that. But, my tunnel is Up, I can ping your endpoint, and it can be pinged from remote location (this is a machine connected to ClaraNet UK): bash-2.05# date Sat Oct 27 09:03:01 GMT 2007 bash-2.05# ping6 2001:6f8:202:160::2 PING 2001:6f8:202:160::2(2001:6f8:202:160::2) from 2001:a88:1::2 : 56 data bytes 64 bytes from 2001:6f8:202:160::2: icmp_seq=0 hops=43 time=118.810 msec 64 bytes from 2001:6f8:202:160::2: icmp_seq=1 hops=43 time=120.105 msec 64 bytes from 2001:6f8:202:160::2: icmp_seq=2 hops=43 time=120.041 msec 64 bytes from 2001:6f8:202:160::2: icmp_seq=3 hops=43 time=112.598 msec --- 2001:6f8:202:160::2 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss Please note I'm not claiming about my 10 points ;) I just want this issue to be solved, as I quite don't see what's going on. Hint : it seems that the problem started at the time I got my subnet allocated and/or configured... Regards, Paul
Tunnel reported unreachable - but it is...
[ch] Jeroen Massar SixXS Staff on Saturday, 27 October 2007 14:24:43
Tunnel reported unreachable - but it is...
[fr] Shadow Hawkins on Saturday, 27 October 2007 17:59:46
Hi Jeroen, Thanks for your answer. Unfortunately, it doesn't seem to apply very easily : there is no not or connection tracking on my side. What's more, if that was the problem, why would it occur now, and never before in the several weeks/months this tunnel is up... I'm not using less. But to make it sure, I'm going to install a "ping6 the tunnel endpoint"-script on my machine, so that any statefull located that could be affected with a slowdown in traffic will keep its state correct. Thanks, Paul
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 27 October 2007 14:24:48
Message is Locked
The state of this ticket has been changed to user

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

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