Username: Password:

Ticket ID: SIXXS #6439922
Ticket Status: Resolved

PoP: ptlis01 - NFSi Telecom, Lda. (Lisboa)

Cannot ping PoP side
[pt] Carmen Sandiego on Saturday, 11 February 2012 12:12:45
I can't ping the PoP side. aiccu test
####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.67) ### 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.67 (192.168.1.67) 56(84) bytes of data. 64 bytes from 192.168.1.67: icmp_req=1 ttl=64 time=0.060 ms 64 bytes from 192.168.1.67: icmp_req=2 ttl=64 time=0.042 ms 64 bytes from 192.168.1.67: icmp_req=3 ttl=64 time=0.042 ms --- 192.168.1.67 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.042/0.048/0.060/0.008 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (82.102.0.131) ### 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 82.102.0.131 (82.102.0.131) 56(84) bytes of data. 64 bytes from 82.102.0.131: icmp_req=1 ttl=57 time=21.5 ms 64 bytes from 82.102.0.131: icmp_req=2 ttl=57 time=20.1 ms 64 bytes from 82.102.0.131: icmp_req=3 ttl=57 time=20.6 ms --- 82.102.0.131 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 20.110/20.788/21.571/0.612 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (82.102.0.131) 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 82.102.0.131 (82.102.0.131), 30 hops max, 60 byte packets 1 dsldevice.lan (192.168.1.254) 27.699 ms 27.371 ms 27.233 ms 2 * * * 3 bl3-74-53.dsl.telepac.pt (213.13.74.53) 31.467 ms 35.122 ms 35.116 ms 4 194.65.12.98 (194.65.12.98) 41.412 ms 44.445 ms 45.944 ms 5 te-1-1.lcatrt1.telepac.net (213.13.135.174) 48.269 ms 51.167 ms 52.521 ms 6 94.46.208.1 (94.46.208.1) 58.717 ms 33.791 ms 37.191 ms 7 cr1-lis.r.nfsi.pt (81.92.223.81) 34.143 ms 35.726 ms 33.637 ms 8 ptlis01.sixxs.net (82.102.0.131) 36.141 ms 33.277 ms 31.677 ms ###### Did this work? [Y/n] ###### [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.042 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.045 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.043 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.042/0.043/0.045/0.005 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:b18:2000:19f::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:b18:2000:19f::2(2001:b18:2000:19f::2) 56 data bytes 64 bytes from 2001:b18:2000:19f::2: icmp_seq=1 ttl=64 time=0.044 ms 64 bytes from 2001:b18:2000:19f::2: icmp_seq=2 ttl=64 time=0.044 ms 64 bytes from 2001:b18:2000:19f::2: icmp_seq=3 ttl=64 time=0.044 ms --- 2001:b18:2000:19f::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.044/0.044/0.044/0.000 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:b18:2000:19f::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:b18:2000:19f::1(2001:b18:2000:19f::1) 56 data bytes --- 2001:b18:2000:19f::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2015ms ###### Did this work? [Y/n] n
ip -6 route show
2001:b18:2000:19f::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 default via 2001:b18:2000:19f::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0
aiccu start
Tunnel Information for T84590: POP Id : ptlis01 IPv6 Local : 2001:b18:2000:19f::2/64 IPv6 Remote : 2001:b18:2000:19f::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled
Thanks in advance, Nelson
State change: resolved
[ch] Jeroen Massar SixXS Staff on Saturday, 11 February 2012 12:20:25
Message is Locked
The state of this ticket has been changed to resolved

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

Not logged in.
©2001-2014 SixXS - IPv6 Deployment & Tunnel Broker