SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #5319394
Ticket Status: Resolved

PoP: ittrn01 - ITgate (Torino)

Tunnel T13832 up, but could not reach PoP endpoint
[it] Shadow Hawkins on Thursday, 04 August 2011 12:41:43
NIC: LBH1-SIXXS Tunnel: T13832 Mode: AYIYA Aiccu correctly sets up the tunnel with no errors, but I'm not able to reach the IPv6 PoP endpoint. IPv4 to the PoP seems to be working fine, though. I also tried setting up a different tunnel (namely T21590) from the same box and this one works fine instead. I also noticed the PoP endpoint is currently unreachable from the outside (eg. tracerouting from another PoP). Thus, I suspect this is not a local issue. Additionally, this tunnel carries a /48 subnet (namely R30825), but shouldn't matter. Here below the AICCU Quick Connectivity Test results. ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.2) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=0.033 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=0.032 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=0.038 ms --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.032/0.034/0.038/0.005 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 213.254.12.34 (213.254.12.34) 56(84) bytes of data. 64 bytes from 213.254.12.34: icmp_req=1 ttl=54 time=49.2 ms 64 bytes from 213.254.12.34: icmp_req=2 ttl=54 time=49.2 ms 64 bytes from 213.254.12.34: icmp_req=3 ttl=54 time=49.4 ms --- 213.254.12.34 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 49.229/49.301/49.404/0.196 ms ###### ####### [3/8] Traceroute to the PoP (213.254.12.34) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 213.254.12.34 (213.254.12.34), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 3.470 ms 4.414 ms 4.403 ms 2 192.168.100.1 (192.168.100.1) 44.913 ms 46.979 ms 49.929 ms 3 host197-63-static.50-88-b.business.telecomitalia.it (88.50.63.197) 52.959 ms 55.556 ms 57.750 ms 4 r-sv24-vl2.opb.interbusiness.it (217.141.108.132) 60.817 ms 63.619 ms 66.206 ms 5 172.17.4.113 (172.17.4.113) 77.241 ms 79.086 ms 81.311 ms 6 172.17.9.17 (172.17.9.17) 84.308 ms 48.649 ms 48.401 ms 7 172.17.4.206 (172.17.4.206) 51.880 ms 54.444 ms 56.913 ms 8 172.17.4.226 (172.17.4.226) 58.379 ms 61.218 ms 64.155 ms 9 itgate-pub.topix.it (194.116.96.4) 67.267 ms 69.295 ms 71.500 ms 10 if-0-1.rumba.edge.TRN.itgate.net (213.254.0.25) 75.041 ms 77.416 ms 80.317 ms 11 frejus.ITgate.net (213.254.12.34) 82.524 ms 85.729 ms 88.098 ms ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.041 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.049 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.041/0.046/0.050/0.008 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:22d::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:1418:100:22d::2(2001:1418:100:22d::2) 56 data bytes 64 bytes from 2001:1418:100:22d::2: icmp_seq=1 ttl=64 time=0.051 ms 64 bytes from 2001:1418:100:22d::2: icmp_seq=2 ttl=64 time=0.056 ms 64 bytes from 2001:1418:100:22d::2: icmp_seq=3 ttl=64 time=0.054 ms --- 2001:1418:100:22d::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.051/0.053/0.056/0.008 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:22d::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was successful then this could be both ### a firewalling and a routing/interface problem PING 2001:1418:100:22d::1(2001:1418:100:22d::1) 56 data bytes --- 2001:1418:100:22d::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2014ms Thanks a lot for your great work, Luca
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 04 August 2011 13:28:06
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