Traffic not flowing through AYIYA Tunnel
Shadow Hawkins on Monday, 30 November 2009 11:12:51
Hi,
I have two AYIYA tunnels that I use in case the other is down. I have a very simple setup, with a public IPv4 IP, no firewall on MacOSX. I use the stock AYIYA configuration and everything has worked fine with one POP (uschi02, which is down). The same setup with the Tunnel to my other POP (usqas01) does not seem to let any traffic flow, although the tunnel is created. I am stumped, because my setup has not changed and it works for one (when it is up) but not for the other.
Any ideas on how to troubleshoot the problem would be appreciated. Thanks!
I use Mac OS 10.6.2 and the TUN/TAP drivers. This is what I get:
On the test everything works until this step:
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1600:20a::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) 2001:4830:1600:20a::2 --> 2001:4830:1600:20a::1
Request timeout for icmp_seq=0
Request timeout for icmp_seq=1
Request timeout for icmp_seq=2
--- 2001:4830:1600:20a::1 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
Aiccu Connection output:
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/10.2.0"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1259090288"
sock_printf() : "username JFB3-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 c96be115d643af82d162c718ab7b4b01"
sock_printf() : "authenticate md5 0bf508b9ee43cda57baaddb0ae6bfd6e"
sock_getline() : "200 Succesfully logged in using md5 as JFB3-SIXXS (Jose Fernando Barbe) from 2001:960:800::2"
sock_printf() : "tunnel show T23740"
sock_getline() : "201 Showing tunnel information for T23740"
sock_getline() : "TunnelId: T23740"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:4830:1600:20a::2"
sock_getline() : "IPv6 POP: 2001:4830:1600:20a::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: usqas01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 66.117.47.228"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: xxxxxxxxxxxx"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T23740
sock_printf() : "QUIT Under the weeping moon"
Tunnel Information for T23740:
POP Id : usqas01
IPv6 Local : 2001:4830:1600:20a::2/64
IPv6 Remote : 2001:4830:1600:20a::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
[tun-start] Trying Configured TUN/TAP interface tun0...
[tun-start] Using TUN/TAP interface tun0
[tun-start] Setting TUNSIFHEAD for tun0
add net default: gateway 2001:4830:1600:20a::1
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
ifconfig:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=1<UP> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:26:4a:12:50:92
media: autoselect status: inactive
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,flow-control> 10baseT/UTP <full-duplex,hw-loopback> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,flow-control> 100baseTX <full-duplex,hw-loopback> 1000baseT <full-duplex> 1000baseT <full-duplex,flow-control> 1000baseT <full-duplex,hw-loopback>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 128.101.33.38 netmask 0xffffff00 broadcast 128.101.33.255
ether 00:26:bb:05:3e:b2
media: autoselect status: active
supported media: autoselect
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:26:4a:ff:fe:12:50:92
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 172.16.53.1 netmask 0xffffff00 broadcast 172.16.53.255
ether 00:50:56:c0:00:01
vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.202.1 netmask 0xffffff00 broadcast 192.168.202.255
ether 00:50:56:c0:00:08
tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1280
inet6 fe80::226:4aff:fe12:5092%tun0 prefixlen 64 scopeid 0x9
inet6 2001:4830:1600:20a::2 --> 2001:4830:1600:20a::1 prefixlen 128
open (pid 2344)
Routing tables:
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 128.101.33.254 UGSc 36 0 en1
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 1 350 lo0
128.101.33/24 link#5 UCS 6 0 en1
128.101.33.5 0:22:41:f9:0:da UHLWI 0 1 en1 583
128.101.33.38 127.0.0.1 UHS 0 9 lo0
128.101.33.43 0:1b:63:5:54:d7 UHLWI 0 1 en1 198
128.101.33.56 0:1f:f3:ba:4b:c5 UHLWI 0 1 en1 820
128.101.33.63 0:1c:b3:b9:17:8d UHLWI 0 1 en1 852
128.101.33.254 0:13:72:3c:72:42 UHLWI 36 0 en1 137
128.101.33.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 en1
169.254 link#5 UCS 0 0 en1
172.16.53/24 link#7 UC 1 0 vmnet1
172.16.53.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 vmnet1
192.168.202 link#8 UC 1 0 vmnet8
192.168.202.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 vmnet8
Internet6:
Destination Gateway Flags Netif Expire
default 2001:4830:1600:20a::1 UGSc tun0
::1 ::1 UH lo0
2001:4830:1600:20a::1 2001:4830:1600:20a::2 UH tun0
2001:4830:1600:20a::2 link#9 UHL lo0
fe80::%lo0/64 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::226:4aff:fe12:5092%tun0 link#9 UHL lo0
ff01::/32 ::1 Um lo0
ff02::/32 ::1 UmC lo0
ff02::/32 fe80::226:4aff:fe12:5092%tun0 UmC tun0
Traffic not flowing through AYIYA Tunnel
Shadow Hawkins on Tuesday, 24 November 2009 20:22:15
Damn! I posted the md5 hashes ...
Traffic not flowing through AYIYA Tunnel
Shadow Hawkins on Tuesday, 08 December 2009 19:59:12
Anyone? Any idea what could I check to make sure it works?
uschi02 works for me when it's up, but not usqas01 with the exact same configuration.
Traffic not flowing through AYIYA Tunnel
Shadow Hawkins on Tuesday, 08 December 2009 20:05:44
This is a stab in the dark, but...
IIRC, the address range changes when you move POP's, so if your /48 has been assigned out of the Chicago pool, it won't work when you try and use the other POP, unless you use one of those IP's
Traffic not flowing through AYIYA Tunnel
Shadow Hawkins on Monday, 14 December 2009 22:17:22
Is your time in sync?
Posting is only allowed when you are logged in. |