SixXS::Sunset 2017-06-06

no traffic in aiccu tunnel
[be] Shadow Hawkins on Wednesday, 13 January 2010 16:32:23
Hi, I am trying to get aiccu to work on a DD-WRT router. The tunnel gets setup but there is no traffic possible through the tunnel. Tunnel Information for T23783: POP Id : bebru01 IPv6 Local : 2001:6f8:202:3fc::2/64 IPv6 Remote : 2001:6f8:202:3fc::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (84.194.241.209) ### 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 84.194.241.209 (84.194.241.209): 56 data bytes 64 bytes from 84.194.241.209: seq=0 ttl=64 time=0.437 ms 64 bytes from 84.194.241.209: seq=1 ttl=64 time=0.331 ms 64 bytes from 84.194.241.209: seq=2 ttl=64 time=0.330 ms --- 84.194.241.209 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.330/0.366/0.437 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.100.184.146) ### 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 212.100.184.146 (212.100.184.146): 56 data bytes 64 bytes from 212.100.184.146: seq=0 ttl=52 time=25.058 ms 64 bytes from 212.100.184.146: seq=1 ttl=52 time=19.373 ms 64 bytes from 212.100.184.146: seq=2 ttl=52 time=18.132 ms --- 212.100.184.146 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 18.132/20.854/25.058 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (212.100.184.146) 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 212.100.184.146 (212.100.184.146), 30 hops max, 38 byte packets 1 d54C2F001.access.telenet.be (84.194.240.1) 11.231 ms 11.008 ms 5.185 ms 2 dD5E0C5C1.access.telenet.be (213.224.197.193) 6.683 ms 9.398 ms 14.149 ms 3 dD5E0FD5D.access.telenet.be (213.224.253.93) 10.817 ms 6.832 ms 7.780 ms 4 dD5E0FD29.access.telenet.be (213.224.253.41) 10.435 ms 7.093 ms 8.878 ms 5 dD5E0FDB9.access.telenet.be (213.224.253.185) 11.182 ms 6.397 ms 5.642 ms 6 TenGigabitEthernet3-3.ar1.NDL1.gblx.net (64.210.31.249) 8.017 ms 9.713 ms te3-2.ar1.NLD1.ANT1.gblx.net (64.215.184.29) 11.676 ms 7 EasyNet-LTD-Schipol.GigabitEthernet3-20.ar4.AMS2.gblx.net (67.17.161.130) 12.322 ms 14.790 ms 13.619 ms 8 te0-0-0.gr11.ixbru.be.easynet.net (87.86.77.54) 22.322 ms 21.734 ms 20.899 ms 9 ge0-2-0-324.br1.ixbru.easynet.net (87.86.71.189) 23.619 ms 23.132 ms 21.834 ms 10 ge3-4.br10.ixbru.be.easynet.net (212.100.162.57) 21.309 ms 22.044 ms 22.318 ms 11 ge3-3.br10.gdbru.be.easynet.net (212.100.162.45) 24.029 ms 24.707 ms 24.449 ms 12 ge0-0.cr3.gdbru.be.easynet.net (212.100.161.14) 23.551 ms 25.143 ms 21.875 ms 13 212.100.184.146 (212.100.184.146) 22.238 ms 22.655 ms 21.027 ms ###### Did this work? [Y/n] y ###### [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: icmp6_seq=0 ttl=64 time=0.2 ms 64 bytes from ::1: icmp6_seq=1 ttl=64 time=0.2 ms 64 bytes from ::1: icmp6_seq=2 ttl=64 time=0.2 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.2/0.2/0.2 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:202:3fc::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:202:3fc::2 (2001:6f8:202:3fc::2): 56 data bytes 64 bytes from 2001:6f8:202:3fc::2: icmp6_seq=0 ttl=64 time=0.2 ms 64 bytes from 2001:6f8:202:3fc::2: icmp6_seq=1 ttl=64 time=0.2 ms 64 bytes from 2001:6f8:202:3fc::2: icmp6_seq=2 ttl=64 time=0.2 ms --- 2001:6f8:202:3fc::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.2/0.2/0.2 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:202:3fc::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 PING 2001:6f8:202:3fc::1 (2001:6f8:202:3fc::1): 56 data bytes --- 2001:6f8:202:3fc::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ###### Did this work? [Y/n] n I checked the firewall but it isn't dropping any packets. Furthermore, a tcpdump on my external interface while pinging Remote/PoP Inner Tunnel Endpoint shows the following: # ping6 2001:6f8:202:3fc::1 PING 2001:6f8:202:3fc::1 (2001:6f8:202:3fc::1): 56 data bytes # tcpdump -n -i vlan2 host 212.100.184.146 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vlan2, link-type EN10MB (Ethernet), capture size 68 bytes 15:28:09.554290 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 15:28:10.564278 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 15:28:11.574277 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 15:28:12.584278 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 When I ping6 2001:6f8:202:3fc::1 (my local inner tunnel endpoint) from another ipv6 host under my control, I see the following on my tcpdump (outgoing ping6 stopped): tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vlan2, link-type EN10MB (Ethernet), capture size 68 bytes 15:30:59.808707 IP 212.100.184.146.5072 > 84.194.241.209.32780: UDP, length 148 15:30:59.809650 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 15:31:00.822851 IP 212.100.184.146.5072 > 84.194.241.209.32780: UDP, length 148 15:31:00.823690 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 15:31:01.821846 IP 212.100.184.146.5072 > 84.194.241.209.32780: UDP, length 148 15:31:01.822693 IP 84.194.241.209.32780 > 212.100.184.146.5072: UDP, length 152 So it seems that my outgoing ipv6 traffic is rejected somewhere along the path. Does anyone has an idea what might be going on here? Thanks, Kind regards, Tom
no traffic in aiccu tunnel
[ch] Jeroen Massar SixXS Staff on Wednesday, 13 January 2010 18:58:02
What version of aiccu do you have and where did you get it from? There where several versions released for OpenWRT which where miscompiled which caused the ethernet header to be included and that... does not work. If you can dump one packet that your host sends to the PoP I can easily tell you if that is the case or not. The PoP sees your AYIYA packets coming in correctly formatted most of the way, but if the above is the case, then it can't do much with the packet.
no traffic in aiccu tunnel
[be] Shadow Hawkins on Thursday, 14 January 2010 08:39:55
Hello Jeroen, Thanks for your quick response! I run the following aiccu version:
# aiccu version AICCU 2007.01.15-console by Jeroen Massar
which I got from http://downloads.openwrt.org/kamikaze/8.09.2/brcm47xx/packages/aiccu_20070115-2.1_mipsel.ipk A dump of one packet going to the POP:
# tcpdump -s 1500 -vvv -X -n -i vlan2 host 212.100.184.146 tcpdump: listening on vlan2, link-type EN10MB (Ethernet), capture size 1500 bytes 07:27:21.341100 IP (tos 0x0, ttl 64, id 25138, offset 0, flags [DF], proto UDP (17), length 180) 84.194.241.209.32783 > 212.100.184.146.5072: [udp sum ok] UDP, length 152 0x0000: 4500 00b4 6232 4000 4011 047c 54c2 f1d1 E...b2@.@..|T... 0x0010: d464 b892 800f 13d0 00a0 bb8a 4152 1129 .d..........AR.) 0x0020: 4b4e c759 2001 06f8 0202 03fc 0000 0000 KN.Y............ 0x0030: 0000 0002 5c5f 4d70 aa4e 5bb9 ed98 e7e9 ....\_Mp.N[..... 0x0040: 291b fd59 d8b9 a42e 0000 86dd 6000 0000 )..Y........`... 0x0050: 0040 3a40 2001 06f8 0202 03fc 0000 0000 .@:@............ 0x0060: 0000 0002 2a00 1450 8001 0000 0000 0000 ....*..P........ 0x0070: 0000 0063 8000 b368 643b 0000 59c7 4e4b ...c...hd;..Y.NK 0x0080: 8632 0500 10e9 c22a ffff ffff 0000 0010 .2.....*........ 0x0090: 30ca 4300 0200 0000 0000 0000 0000 0000 0.C............. 0x00a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00b0: 0000 0000 ....
Or if you like a more wireshark friendly dump : download here Kind regards, Tom
no traffic in aiccu tunnel
[be] Shadow Hawkins on Thursday, 14 January 2010 09:12:36
Meanwhile, I investigated with your hint and I was indeed running a version of aiccu which was not compiled correctly. Installing a more recent version made it work. Thanks again for your support! Kind regards, Tom
no traffic in aiccu tunnel
[it] Shadow Hawkins on Tuesday, 02 February 2010 01:11:08
Hi Tom, Same problem here.. Where did you get the aiccu version you installed? Thanks in Advance, Enrico.

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker