Tickets - Problem pinging the remote ipv6 address :: SixXS

Ticket ID: SIXXS #3434593
Ticket Status: Resolved

PoP: chgva01 - IP-Max Network Services (Geneva)

Problem pinging the remote ipv6 address

Shadow Hawkins on Thursday, 20 January 2011 17:56:45

Hi, I have a problem pinging the remote node connecting to chgva01. My diagnostics were the following : - aiccu-mac-i386 autotest with verbose and no daemon : works up to the step 6/8 (output is down in the mail) - tcpdump on the interface shows that the packet gets out encapsulated with the correct pop, however nothing comes back from the pop. - Doing a ping6 to the remote node doesnt get any answer. - Doing a ping6 from another device on v6 connected to the same pop doesn't work either, both of the ip (remote and local) aren't reachable. - I had the same beahaviour from 3 different location, some on static public ipv4 some on private nated with differents ISPs. - Last test location is a simple linksys nat box with a dhcp lan behind. - OS is MacOSX 10.5 and last aiccu . - Hope I didn't forgot anything, but I guess something is buggy on pop's side. Aiccu autotest

./aiccu-mac-i386 autotest sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-darwin Darwin/9.8.0" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1295534686" sock_printf() : "username WVG3-SIXXS" sock_getline() : "200 WVG3-SIXXS choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 daf019dd85f68b91df623c9bb59a6fe6" sock_printf() : "authenticate md5 249f910f20191dd3941574d7a67408eb" sock_getline() : "200 Successfully logged in using md5 as WVG3-SIXXS (Will van Gulik)" sock_printf() : "tunnel list" sock_getline() : "201 Listing tunnels" sock_getline() : "T51593 2a02:2528:ff00:2::2 ayiya chgva01" sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>" sock_printf() : "tunnel show T51593" sock_getline() : "201 Showing tunnel information for T51593" sock_getline() : "TunnelId: T51593" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2a02:2528:ff00:2::2" sock_getline() : "IPv6 POP: 2a02:2528:ff00:2::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: chgva01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 46.20.243.4" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: ..." sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T51593 sock_printf() : "QUIT It was lovely talking to you again" Tunnel Information for T51593: POP Id : chgva01 IPv6 Local : 2a02:2528:ff00:2::2/64 IPv6 Remote : 2a02:2528:ff00:2::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [tun-start] Trying Configured TUN/TAP interface sixxs... [tun-start] Trying TUN/TAP interface 0... [tun-start] Using TUN/TAP interface tun0 [tun-start] Setting TUNSIFHEAD for tun0 add net default: gateway 2a02:2528:ff00:2::1 [AYIYA-start] : Anything in Anything (draft-02) heartbeat_socket() - IPv4 : 172.16.4.10 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (172.16.4.10) ### 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 [AYIYA-tun->tundev] : (Socket to TUN) started PING 172.16.4.10 (172.16.4.10): 56 data bytes 64 bytes from 172.16.4.10: icmp_seq=0 ttl=64 time=0.086 ms 64 bytes from 172.16.4.10: icmp_seq=1 ttl=64 time=0.060 ms 64 bytes from 172.16.4.10: icmp_seq=2 ttl=64 time=0.040 ms --- 172.16.4.10 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.040/0.062/0.086/0.019 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (46.20.243.4) ### 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 46.20.243.4 (46.20.243.4): 56 data bytes 64 bytes from 46.20.243.4: icmp_seq=0 ttl=56 time=118.130 ms 64 bytes from 46.20.243.4: icmp_seq=1 ttl=56 time=9.876 ms 64 bytes from 46.20.243.4: icmp_seq=2 ttl=56 time=10.650 ms --- 46.20.243.4 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 9.876/46.219/118.130/50.850 ms ###### ####### [3/8] Traceroute to the PoP (46.20.243.4) 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 46.20.243.4 (46.20.243.4), 64 hops max, 40 byte packets 1 172.16.4.254 (172.16.4.254) 1.998 ms 1.160 ms 1.245 ms 2 gve-gix-as-10-01-lb-0.vtxnet.net (212.147.11.51) 41.080 ms 64.360 ms 108.845 ms 3 gve-gix-cr-76-01-ge-2-3.vtxnet.net (212.147.63.174) 111.062 ms 111.163 ms 222.899 ms 4 gve-gix-br-a1-01-ge-0-0-0.vtxnet.net (212.147.63.37) 108.553 ms 111.349 ms 114.121 ms 5 ip-max.rc01.gva253.ip-max.net (192.65.185.244) 124.295 ms 116.627 ms 116.561 ms 6 ge3-1.cr01.gva253.ip-max.net (193.28.181.17) 111.397 ms 116.563 ms 116.464 ms 7 ge3-15.ar01.gva253.ip-max.net (193.28.181.202) 116.699 ms 119.482 ms 118.801 ms 8 ge0-0.gv1.ip-max.sixxs.net (46.20.240.194) 116.578 ms 119.133 ms 116.535 ms 9 chgva01.sixxs.net (46.20.243.4) 116.585 ms 119.090 ms 125.070 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 PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1 time=0.24 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1 time=0.202 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1 time=0.203 ms --- ::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.202/0.215/0.240 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a02:2528:ff00:2::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING6(56=40+8+8 bytes) 2a02:2528:ff00:2::2 --> 2a02:2528:ff00:2::2 16 bytes from 2a02:2528:ff00:2::2: Echo Request 16 bytes from 2a02:2528:ff00:2::2, icmp_seq=0 hlim=64 dst=2a02:2528:ff00:2::2 time=0.345 ms 16 bytes from 2a02:2528:ff00:2::2: Echo Request 16 bytes from 2a02:2528:ff00:2::2, icmp_seq=1 hlim=64 dst=2a02:2528:ff00:2::2 time=0.229 ms 16 bytes from 2a02:2528:ff00:2::2: Echo Request 16 bytes from 2a02:2528:ff00:2::2, icmp_seq=2 hlim=64 dst=2a02:2528:ff00:2::2 time=0.223 ms --- 2a02:2528:ff00:2::2 ping6 statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.223/0.266/0.345 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a02:2528:ff00:2::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 succesful then this could be both ### a firewalling and a routing/interface problem PING6(56=40+8+8 bytes) 2a02:2528:ff00:2::2 --> 2a02:2528:ff00:2::1 ^C --- 2a02:2528:ff00:2::1 ping6 statistics --- 3 packets transmitted, 0 packets received, 100% packet loss

(Breaked that because obviously, if my gateway is unreachable, I wont be able to trace to the outside world) ifconfig

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:17:f2:30:ac:57 media: autoselect status: inactive supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030 lladdr 00:17:f2:ff:fe:85:be:6e media: autoselect <full-duplex> status: inactive supported media: autoselect <full-duplex> en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::217:f2ff:fe51:ccc0%en1 prefixlen 64 scopeid 0x6 inet 172.16.4.10 netmask 0xffffff00 broadcast 172.16.4.255 ether 00:17:f2:51:cc:c0 media: autoselect status: active supported media: autoselect en2: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 ether 00:16:cb:32:14:aa media: autoselect status: inactive supported media: none autoselect 10baseT/UTP <half-duplex> tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1280 inet6 fe80::217:f2ff:fe30:ac57%tun0 prefixlen 64 scopeid 0x8 inet6 2a02:2528:ff00:2::2 --> 2a02:2528:ff00:2::1 prefixlen 128 open (pid 319)

netstat -rn

Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 172.16.4.254 UGSc 104 0 en1 127 127.0.0.1 UCS 0 0 lo0 127.0.0.1 127.0.0.1 UH 2 98 lo0 169.254 link#6 UCS 0 0 en1 172.16.4/24 link#6 UCS 3 0 en1 172.16.4.10 127.0.0.1 UHS 0 6 lo0 172.16.4.249 0:1:d2:3:f5:41 UHLW 2 312 en1 1187 172.16.4.254 0:18:39:d0:a:4a UHLW 121 54 en1 1195 172.16.4.255 ff:ff:ff:ff:ff:ff UHLWb 0 2 en1 Internet6: Destination Gateway Flags Netif Expire default 2a02:2528:ff00:2::1 UGSc tun0 ::1 link#1 UHL lo0 2a02:2528:ff00:2::1 2a02:2528:ff00:2::2 UH tun0 2a02:2528:ff00:2::2 link#8 UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#1 UHL lo0 fe80::%en1/64 link#6 UC en1 fe80::217:f2ff:fe51:ccc0%en1 0:17:f2:51:cc:c0 UHL lo0 fe80::217:f2ff:fe30:ac57%tun0 link#8 UHL lo0 ff01::/32 ::1 U lo0 ff02::/32 fe80::1%lo0 UC lo0 ff02::/32 link#6 UC en1 ff02::/32 fe80::217:f2ff:fe30:ac57%tun0 UC tun0

Thanks !

State change: resolved Locked

Jeroen Massar SixXS Staff

on Thursday, 20 January 2011 17:59:32

The state of this ticket has been changed to resolved

Problem pinging the remote ipv6 address

Jeroen Massar SixXS Staff

on Thursday, 20 January 2011 18:00:55

- Hope I didn't forgot anything, but I guess something is buggy on pop's side.

Time was not properly synced, it is now. When you re-enable your client it should come up properly.

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