Tickets - Tunnel appears up but no connectivity :: SixXS

Ticket ID: SIXXS #673544
Ticket Status: Resolved

PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 18 February 2008 21:20:00

Tunnel appears to be up but there is no connectivity. Cannot ping PoP endpoint from a native v6 address. aiccu test fails at step 6, ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:97::1) Using the latest aiccu in debian Etch. Brian McPherson BMG1-SIXXS

State change: invalid Locked

Jeroen Massar SixXS Staff

on Monday, 18 February 2008 21:21:51

The state of this ticket has been changed to invalid

Tunnel appears up but no connectivity

Jeroen Massar SixXS Staff

on Monday, 18 February 2008 21:22:14

"It is broken" Please provide more information as clearly requested.

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 18 February 2008 21:33:29

Greetings, I apologize if the information I presented was insufficent. The tunnel I am experiencing this problem on is T14138. AICCU version is: AICCU 2007.01.15-console-linux by Jeroen Massar terra:~# uname -a Linux terra 2.6.18-6-amd64 #1 SMP Wed Jan 23 06:27:23 UTC 2008 x86_64 GNU/Linux Here is a traceroute from a machine I have native v6 on: osiris:~# traceroute6 2001:4978:f:97::1 traceroute to 2001:4978:f:97::1 (2001:4978:f:97::1) from 2001:48a8:0:8:0:3:0:232, 30 hops max, 16 byte packets 1 mx960-07-001-cec.tc.mtu.edu (2001:48a8:0:8::1) 0.698 ms 0.476 ms 1.314 ms 2 j6350-07-001.tc.mtu.edu (2001:48a8:ff:63::2) 3.54 ms 3.193 ms 2.679 ms 3 2001:48a8:1fff::1 (2001:48a8:1fff::1) 1.814 ms 1.215 ms 1.648 ms 4 2001:48a8:48ff::9 (2001:48a8:48ff::9) 18.957 ms 19.328 ms 19.19 ms 5 2001:468:143f::19 (2001:468:143f::19) 20.735 ms 25.42 ms 21.208 ms 6 2001:468:ff:254::1 (2001:468:ff:254::1) 27.502 ms 27.441 ms 23.632 ms 7 2001:468:ff:209::1 (2001:468:ff:209::1) 37.331 ms 37.664 ms 36.676 ms 8 2001:468:ff:609::2 (2001:468:ff:609::2) 54.856 ms 48.929 ms 47.201 ms 9 2001:450:2008:21::1 (2001:450:2008:21::1) 45.298 ms 43.478 ms 44.648 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 sixxs.cx01.chi.bb6.your.org (2001:4978:1:400:202:b3ff:feb4:59cb) 183.723 ms !H 158.662 ms !H 158.076 ms !H This is the full output from the aiccu test: ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (74.126.15.68) ### 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 74.126.15.68 (74.126.15.68) 56(84) bytes of data. 64 bytes from 74.126.15.68: icmp_seq=1 ttl=64 time=0.026 ms 64 bytes from 74.126.15.68: icmp_seq=2 ttl=64 time=0.035 ms 64 bytes from 74.126.15.68: icmp_seq=3 ttl=64 time=0.038 ms --- 74.126.15.68 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 0.026/0.033/0.038/0.005 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22) ### 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 216.14.98.22 (216.14.98.22) 56(84) bytes of data. 64 bytes from 216.14.98.22: icmp_seq=1 ttl=55 time=6.89 ms 64 bytes from 216.14.98.22: icmp_seq=2 ttl=55 time=12.0 ms 64 bytes from 216.14.98.22: icmp_seq=3 ttl=55 time=7.30 ms --- 216.14.98.22 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2008ms rtt min/avg/max/mdev = 6.893/8.758/12.075/2.351 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (216.14.98.22) 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 216.14.98.22 (216.14.98.22), 30 hops max, 52 byte packets 1 keymaster-ccust-vlan02-rtr.bendorius.net (74.126.15.66) 0.479 ms 0.400 ms 0.381 ms 2 66.103.225.177 (66.103.225.177) 0.797 ms 0.838 ms 0.694 ms 3 ge-6-11-262.car2.Detroit1.Level3.net (4.79.14.5) 0.853 ms 0.884 ms 0.836 ms 4 ae-11-11.car1.Detroit1.Level3.net (4.69.133.245) 0.951 ms 0.846 ms 0.831 ms 5 ae-8-8.ebr2.Chicago1.Level3.net (4.69.133.242) 6.000 ms 14.896 ms 15.638 ms 6 ae-23-54.car3.Chicago1.Level3.net (4.68.101.103) 6.588 ms ae-23-56.car3.Chicago1.Level3.net (4.68.101.167) 6.515 ms ae-23-52.car3.Chicago1.Level3.net (4.68.101.39) 7.007 ms 7 261.xe-0-3-0.cr2.ord1.us.scnet.net (4.71.100.26) 3.439 ms 6.935 ms 7.181 ms 8 v21.ar2.ord1.us.scnet.net (216.246.95.244) 19.640 ms v21.ar1.ord1.us.scnet.net (216.246.95.243) 7.918 ms 7.526 ms 9 sce.bg0.ord01.gw.stilenet.com (64.202.111.33) 6.876 ms sce.bg0-v4.ord01.gw.stilenet.com (64.202.111.37) 3.822 ms sce.bg0.ord01.gw.stilenet.com (64.202.111.33) 5.684 ms 10 sixxs.cx01.chi.bb.your.org (216.14.98.22) 6.080 ms 6.790 ms 6.327 ms ###### Did this work? [Y/n] y PING 2001:4978:f:97::1(2001:4978:f:97::1) 56 data bytes --- 2001:4978:f:97::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2001ms ###### Did this work? [Y/n] 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.035 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.042 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.038 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.035/0.038/0.042/0.005 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4978:f:97::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4978:f:97::2(2001:4978:f:97::2) 56 data bytes 64 bytes from 2001:4978:f:97::2: icmp_seq=1 ttl=64 time=0.000 ms 64 bytes from 2001:4978:f:97::2: icmp_seq=2 ttl=64 time=0.000 ms 64 bytes from 2001:4978:f:97::2: icmp_seq=3 ttl=64 time=0.000 ms --- 2001:4978:f:97::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:97::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 Please let me know if there is more information you need. -- Brian McPherson BMG1-SIXXS

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 18 February 2008 21:35:20

whoops, slight reordering problem when pasting multiple things. This should be at the bottom of the tests, instead of in the middle. PING 2001:4978:f:97::1(2001:4978:f:97::1) 56 data bytes --- 2001:4978:f:97::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2001ms ###### Did this work? [Y/n] n -- Brian McPherson BMG1-SIXXS

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 18 February 2008 21:41:43

terra:~# ip -6 adddr Object "adddr" is unknown, try "ip help". terra:~# ip -6 addr 1: lo: <LOOPBACK,UP,10000> mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 7: sixxs@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1280 inet6 2001:4978:f:97::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4a7e:f44/128 scope link valid_lft forever preferred_lft forever terra:~# ip -6 route 2001:4978:f:97::/64 via :: dev sixxs metric 256 expires 21334270sec mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 via :: dev sixxs metric 256 expires 21334270sec mtu 1280 advmss 1220 hoplimit 4294967295 ff00::/8 dev sixxs metric 256 expires 21334270sec mtu 1280 advmss 1220 hoplimit 4294967295 default via 2001:4978:f:97::1 dev sixxs metric 1024 expires 21334270sec mtu 1280 advmss 1220 hoplimit 4294967295 terra:~# ip -4 route 74.126.15.64/27 dev eth0 proto kernel scope link src 74.126.15.68 default via 74.126.15.65 dev eth0 src 74.126.15.75 terra:~# ip -4 addr 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 inet 74.126.15.68/27 brd 74.126.15.95 scope global eth0 inet 74.126.15.69/27 brd 74.126.15.95 scope global secondary eth0:0 inet 74.126.15.82/27 brd 74.126.15.95 scope global secondary eth0:1 inet 74.126.15.74/27 brd 74.126.15.95 scope global secondary eth0:5 inet 74.126.15.75/27 brd 74.126.15.95 scope global secondary eth0:6 inet 74.126.15.76/27 brd 74.126.15.95 scope global secondary eth0:7 inet 74.126.15.77/27 brd 74.126.15.95 scope global secondary eth0:8 inet 74.126.15.88/27 brd 74.126.15.95 scope global secondary eth0:10 -- Brian McPherson BMG1-SIXXS

Tunnel appears up but no connectivity

Jeroen Massar SixXS Staff

on Monday, 18 February 2008 22:30:15

You have multiple IPv4 addresses there. AICCU does not set the 'local' IPv4 address of an IPv4 in IPv6 tunnel. As such it might happen that packets are sourced from the wrong address. In this scenario (static IPv6 in IPv4 tunnel) one can better use the system configuration method of configuring the tunnel, especially as one is then able to configure the local IPv4 address also. AICCU is intended for easy configuration, not for a catch all solve all. Doing tcpdumps might reveal that it is selecting a different source address.

Tunnel appears up but no connectivity

Jeroen Massar SixXS Staff

on Monday, 18 February 2008 21:43:16

osiris:~# traceroute6 2001:4978:f:97::1

[..] Which only demonstrates that you have a connectivity problem somewhere. The !H might indicate that the PoP doesn't have the tunnel configured. The 'aiccu test' results only show that your connectivity is not working. Output of actual configuration information, like routing table, interface list etc etc, as requested in the "Reporting Problems" list might actually show if that is correctly configured or most likely not. tcpdumps are of course also very handy as requested there.

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 18 February 2008 21:49:11

Greetings, I have posted the routing tables, but am unsure what to add for tcp dump. The tunnel was working until approximately 14:12 EST, when it stopped without any modification of any of the ip addresses or routing table. -- Brian McPherson BMG1-SIXXS

Tunnel appears up but no connectivity

Jeroen Massar SixXS Staff

on Monday, 18 February 2008 22:25:12

This involves computers, they tend to exhibit random behavior.

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 18 February 2008 22:18:34

Greetings, I waited another 15 minutes and tried restarting the tunnel and everything seemed to come back up fine. I tried more than a dozen times to restart and reload everything before posting here so I don't think it was anything on my end. This ticket may be closed now, Thanks. -- Brian McPherson BMG1-SIXXS

State change: resolved Locked

Jeroen Massar SixXS Staff

on Monday, 18 February 2008 22:30:35

The state of this ticket has been changed to resolved

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 29 September 2008 04:26:22

I am having this issue today, it appears others may also as the traffic graph for this pop is showing very little today, compared to yesterday. When I run aiccu test, it fails at the ping6. Pings will not get through to the pop end of the tunnel or sixxs.net, I can ping my side of the tunnel and any internal addresses on my subnet. The IPv4 address for the pop is working. Nothing has changed on my end, it was working fine yesterday. I have restarted aiccu and the system with no change. Sep 28 21:17:07 (none) local7.info syslog: Succesfully retrieved tunnel information for T16945 Sep 28 21:17:08 (none) local7.info syslog: AICCU running as PID 1916 Sep 28 21:17:08 (none) local7.info syslog: [AYIYA-start] : Anything in Anything (draft-02) Sep 28 21:17:08 (none) local7.info syslog: [AYIYA-tun->tundev] : (Socket to TUN) started root@Linky:~# ping6 2001:4978:f:1a7::1 PING 2001:4978:f:1a7::1 (2001:4978:f:1a7::1): 56 data bytes --- 2001:4978:f:1a7::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss root@Linky:~# ip -6 route show 2001:4978:f:1a7::/64 dev sixxs metric 256 mtu 1280 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev br-lan metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth0.1 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth0.0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev wl0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev sixxs metric 256 mtu 1280 advmss 1220 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev br-lan metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth0.1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth0.0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev wl0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 default via 2001:4978:f:1a7::1 dev sixxs metric 1024 mtu 1280 advmss 1220

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 29 September 2008 04:31:12

I should mention this is running OpenWRT Kamikaze, with aiccu "20070115-1" Linux Linky 2.4.34 #94 Tue Sep 9 02:58:48 CDT 2008 mips unknown There is one nat in front of this box with a DMZ going to this one.

Tunnel appears up but no connectivity

Jeroen Massar SixXS Staff

on Monday, 29 September 2008 11:32:57

Please provide the details from the "Reporting Problems" section on the Contact page, without that information we can't do much.

Tunnel appears up but no connectivity

Shadow Hawkins on Monday, 29 September 2008 14:17:26

It appears to have sorted itself out overnight, as traffic is now going through and I can ping the pop end of the tunnel.

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