Ticket ID: SIXXS #6145398 Ticket Status: Resolved PoP: nlede01 - BIT BV (Ede)
Not receiving AYIYA replies for tunnel T84634
Shadow Hawkins on Saturday, 24 December 2011 15:54:43
As of yesterday evening, I seem to no longer receive AYIYA UDP traffic from the nlede01 pop. As far as I can determine, IPv4 connectivity is unimpeded (NAT forwards that worked previously unchanged), verified using tcpdump. AICCU appears to provide the correct tunnel details on its verbose mode. I included its test output below.
Are you receiving my UDP traffic? And if so, do you see any reason on your end why I would not receive answers?
Handle: RAK24-6BONE
Tunnel: T84634 (AYIYA)
IPv4 endpoint: 80.101.106.11
IPv6 endpoint: 2001:7b8:2ff:42b::2
Platform
Platform: OpenBSD sol.iverdahl.net 4.9 GENERIC#4 i386
AICCU: AICCU 2007.01.15-console-openbsd by Jeroen Massar
Connection: using rl0 (NAT'ed by DSL modem) interface
Verified both with SpeedTouch 716 and FritzBox 7360 modems
Firewall: PF, configuration unchanged from earlier working state
AICCU output
# aiccu start
Tunnel Information for T84634:
POP Id : nlede01
IPv6 Local : 2001:7b8:2ff:42b::2/64
IPv6 Remote : 2001:7b8:2ff:42b::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
# aiccu autotest
add net default: gateway 2001:7b8:2ff:42b::1
Tunnel Information for T84634:
POP Id : nlede01
IPv6 Local : 2001:7b8:2ff:42b::2/64
IPv6 Remote : 2001:7b8:2ff:42b::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.178.20)
### 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.178.20 (192.168.178.20): 56 data bytes
64 bytes from 192.168.178.20: icmp_seq=0 ttl=255 time=0.092 ms
64 bytes from 192.168.178.20: icmp_seq=1 ttl=255 time=0.072 ms
64 bytes from 192.168.178.20: icmp_seq=2 ttl=255 time=0.069 ms
--- 192.168.178.20 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.069/0.077/0.092/0.014 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (193.109.122.244)
### 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 193.109.122.244 (193.109.122.244): 56 data bytes
64 bytes from 193.109.122.244: icmp_seq=0 ttl=59 time=19.237 ms
64 bytes from 193.109.122.244: icmp_seq=1 ttl=59 time=18.571 ms
64 bytes from 193.109.122.244: icmp_seq=2 ttl=59 time=18.642 ms
--- 193.109.122.244 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 18.571/18.816/19.237/0.338 ms
######
####### [3/8] Traceroute to the PoP (193.109.122.244) 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 193.109.122.244 (193.109.122.244), 64 hops max, 40 byte packets
1 192.168.178.1 (192.168.178.1) 0.253 ms 0.216 ms 0.172 ms
2 lo1.dr4.d12.xs4all.net (194.109.5.227) 37.900 ms 17.151 ms 24.89 ms
3 1314.ae3.xr3.3d12.xs4all.net (194.109.7.133) 16.619 ms 16.695 ms 17.39 ms
4 0.ge-1-2-0.xr1.sara.xs4all.net (194.109.5.6) 16.816 ms 17.397 ms 17.113 ms
5 amsix-501.xe-0-0-0.jun1.bit-2a.network.bit.nl (195.69.144.35) 19.24 ms 19.222 ms 18.411 ms
6 nlede01.sixxs.net (193.109.122.244) 19.337 ms !N 18.770 ms !N 18.414 ms !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
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%5 time=0.088 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1%5 time=0.075 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1%5 time=0.064 ms
--- ::1 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.064/0.076/0.088/0.010 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:7b8:2ff:42b::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) 2001:7b8:2ff:42b::2 --> 2001:7b8:2ff:42b::2
16 bytes from 2001:7b8:2ff:42b::2: Echo Request
16 bytes from 2001:7b8:2ff:42b::2, icmp_seq=0 hlim=64 dst=2001:7b8:2ff:42b::2%5 time=0.097 ms
16 bytes from 2001:7b8:2ff:42b::2: Echo Request
16 bytes from 2001:7b8:2ff:42b::2, icmp_seq=1 hlim=64 dst=2001:7b8:2ff:42b::2%5 time=0.087 ms
16 bytes from 2001:7b8:2ff:42b::2: Echo Request
16 bytes from 2001:7b8:2ff:42b::2, icmp_seq=2 hlim=64 dst=2001:7b8:2ff:42b::2%5 time=0.07 ms
--- 2001:7b8:2ff:42b::2 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.070/0.085/0.097/0.011 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:7b8:2ff:42b::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
--- 2001:7b8:2ff:42b::1 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:7b8:2ff:42b::2, 64 hops max, 12 byte packets
1 * * *
2 * * *
3 * * *
<repeating timeouts>
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute6 to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:7b8:2ff:42b::2, 64 hops max, 12 byte packets
1 * * *
2 * * *
3 * * *
<repeating timeouts>
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
Interface table
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33200
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
age0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:1b:fc:d9:a0:27
priority: 0
media: Ethernet autoselect (none)
status: no carrier
rl0: flags=28b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6> mtu 1500
lladdr 00:e0:4c:3c:5b:0d
description: Krieger - Uplink
priority: 0
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.178.20 netmask 0xffffff00 broadcast 192.168.178.255
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:1b:21:71:61:d0
description: Krieger - Sol system
priority: 0
media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
status: active
inet 192.168.30.10 netmask 0xffffff00 broadcast 192.168.30.255
inet6 fe80::21b:21ff:fe71:61d0%em0 prefixlen 64 scopeid 0x3
inet6 2001:7b8:3a6:10::1 prefixlen 64
enc0: flags=0<>
priority: 0
groups: enc
status: active
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33200
priority: 0
groups: pflog
pflog6: flags=41<UP,RUNNING> mtu 33200
description: Logged traffic (IPv6)
priority: 0
groups: pflog
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
priority: 0
groups: tun egress
status: active
inet6 fe80::21b:fcff:fed9:a027%tun0 -> prefixlen 64 scopeid 0xa
inet6 fe80::4b8:2ff:42b:2%tun0 -> prefixlen 64 scopeid 0xa
inet6 2001:7b8:2ff:42b::2 -> 2001:7b8:2ff:42b::1 prefixlen 128
Routing table
# netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Prio Iface
default 192.168.178.1 UGS 8 22950 - 8 rl0
127/8 127.0.0.1 UGRS 0 0 33200 8 lo0
127.0.0.1 127.0.0.1 UH 14 364318 33200 4 lo0
192.168.10/24 192.168.30.10 UGS 0 434 - 8 em0
192.168.30/24 link#3 UC 4 0 - 4 em0
192.168.30.1 127.0.0.1 UGHS 1 3966 33200 8 lo0
192.168.30.1/32 link#3 UC 0 0 - 4 em0
192.168.30.10 00:1b:21:71:61:d0 UHLc 1 0 - 4 lo0
192.168.30.30 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.30/32 link#3 UC 0 0 - 4 em0
192.168.30.31 127.0.0.1 UGHS 0 2 33200 8 lo0
192.168.30.31/32 link#3 UC 0 0 - 4 em0
192.168.30.32 127.0.0.1 UGHS 0 2 33200 8 lo0
192.168.30.32/32 link#3 UC 0 0 - 4 em0
192.168.30.33 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.33/32 link#3 UC 0 0 - 4 em0
192.168.30.34 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.34/32 link#3 UC 0 0 - 4 em0
192.168.30.35 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.35/32 link#3 UC 0 0 - 4 em0
192.168.30.36 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.36/32 link#3 UC 0 0 - 4 em0
192.168.30.37 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.37/32 link#3 UC 0 0 - 4 em0
192.168.30.38 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.38/32 link#3 UC 0 0 - 4 em0
192.168.30.39 127.0.0.1 UGHS 0 0 33200 8 lo0
192.168.30.39/32 link#3 UC 0 0 - 4 em0
192.168.30.53 00:11:50:a9:15:7e UHLc 3 4803 - 4 em0
192.168.30.207 b8:ff:61:2b:76:88 UHLc 1 90 - 4 em0
192.168.30.209 dc:2b:61:4f:f3:d8 UHLc 0 97 - 4 em0
192.168.178/24 link#2 UC 1 0 - 4 rl0
192.168.178.1 c0:25:06:57:85:86 UHLc 1 8423 - 4 rl0
192.168.178.20 127.0.0.1 UGHS 0 15 33200 8 lo0
224/4 127.0.0.1 URS 0 0 33200 8 lo0
Internet6:
Destination Gateway Flags Refs Use Mtu Prio Iface
::/104 ::1 UGRS 0 0 - 8 lo0
::/96 ::1 UGRS 0 0 - 8 lo0
default 2001:7b8:2ff:42b::1 UGS 1 44 - 8 tun0
::1 ::1 UH 14 30 33200 4 lo0
::127.0.0.0/104 ::1 UGRS 0 0 - 8 lo0
::224.0.0.0/100 ::1 UGRS 0 0 - 8 lo0
::255.0.0.0/104 ::1 UGRS 0 0 - 8 lo0
::ffff:0.0.0.0/96 ::1 UGRS 0 0 - 8 lo0
2001:7b8:2ff:42b::1 2001:7b8:2ff:42b::2 UH 1 0 - 4 tun0
2001:7b8:2ff:42b::2 link#10 UHL 0 0 - 4 lo0
2001:7b8:3a6:10::/64 link#3 UC 0 0 - 4 em0
2001:7b8:3a6:10::1 00:1b:21:71:61:d0 UHL 0 0 - 4 lo0
2002::/24 ::1 UGRS 0 0 - 8 lo0
2002:7f00::/24 ::1 UGRS 0 0 - 8 lo0
2002:e000::/20 ::1 UGRS 0 0 - 8 lo0
2002:ff00::/24 ::1 UGRS 0 0 - 8 lo0
fe80::/10 ::1 UGRS 53 0 - 8 lo0
fe80::%em0/64 link#3 UC 0 0 - 4 em0
fe80::21b:21ff:fe71:61d0%em0 00:1b:21:71:61:d0 UHL 0 0 - 4 lo0
fe80::%lo0/64 fe80::1%lo0 U 0 0 - 4 lo0
fe80::1%lo0 link#5 UHL 0 0 - 4 lo0
fe80::%tun0/64 fe80::21b:fcff:fed9:a027%tun0 U 0 0 - 4 tun0
fe80::21b:fcff:fed9:a027%tun0 link#10 UHL 0 0 - 4 lo0
fe80::4b8:2ff:42b:2%tun0 link#10 UHL 0 0 - 4 lo0
fec0::/10 ::1 UGRS 0 0 - 8 lo0
ff01::/16 ::1 UGRS 0 0 - 8 lo0
ff01::%rl0/32 link#2 UC 0 0 - 4 rl0
ff01::%em0/32 link#3 UC 0 0 - 4 em0
ff01::%lo0/32 ::1 UC 0 0 - 4 lo0
ff01::%tun0/32 fe80::21b:fcff:fed9:a027%tun0 UC 0 0 - 4 tun0
ff02::/16 ::1 UGRS 28 0 - 8 lo0
ff02::%em0/32 link#3 UC 6 0 - 4 em0
ff02::1:ff20:a7ee%em0 link#3 UHLc 0 0 - 4 em0
ff02::1:ff28:2d6b%em0 link#3 UHLc 0 0 - 4 em0
ff02::1:ff58:7abb%em0 link#3 UHLc 0 0 - 4 em0
ff02::1:ff6c:855f%em0 link#3 UHLc 0 0 - 4 em0
ff02::1:ffea:ed8e%em0 link#3 UHLc 0 0 - 4 em0
ff02::1:ffed:23dc%em0 link#3 UHLc 0 0 - 4 em0
ff02::%lo0/32 ::1 UC 0 0 - 4 lo0
ff02::%tun0/32 fe80::21b:fcff:fed9:a027%tun0 UC 0 0 - 4 tun0
Encap:
Source Port Destination Port Proto SA(Address/Proto/Type/Direction)
192.168.10/24 0 192.168.30/24 0 0 130.161.83.99/esp/use/in
192.168.30/24 0 192.168.10/24 0 0 130.161.83.99/esp/require/out
172.24.8/24 0 192.168.30/24 0 0 213.189.8.47/esp/use/in
192.168.30/24 0 172.24.8/24 0 0 213.189.8.47/esp/require/out
Clock-sync check
# rdate -np ntp.xs4all.nl; date
Sat Dec 24 15:24:06 CET 2011
Sat Dec 24 15:24:06 CET 2011
State change: resolved
Jeroen Massar on Saturday, 24 December 2011 17:37:51
The state of this ticket has been changed to resolved
Posting is only allowed when you are logged in. |