Forum - Problems with OpenWRT :: SixXS - IPv6 Deployment & Tunnel Broker

Problems with OpenWRT

Shadow Hawkins on Thursday, 14 June 2007 02:00:54

Hi, I've been trying to install AYIYA tunnel on OpenWRT by following these steps : -installing X-WRT wich is based on the latest Kamikaze -following steps 2. and 3. from http://wiki.openwrt.org/IPv6_howto -installing AICCU from backports 0.9 -configuring AICCU -adding some route info for the subnet (as said in step 5. of the OpenWRT howto) :

ip -6 addr add 2001:6f8:3cd::/64 dev br0 ip -6 route add 2001:6f8:3cd::/64 dev br0

-starting AICCU Starting aiccu did not report any problem but after a while, I got this message in the logs : sixxs: no IPv6 routers present I tried to ping6 : local sixxs interface 2001:(...):2 is ok but the PoP 2001:(...):1 is unreachable. I also tried this :

~$ ip -6 route show 2001:6f8:202:1b7::/64 dev sixxs metric 256 mtu 1280 advmss 1220 2001:6f8:3cd::/64 dev br0 metric 256 mtu 1500 advmss 1440 2001:6f8:3cd::/64 dev br0 metric 1024 mtu 1500 advmss 1440 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 fe80::/64 dev br0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan1 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 vlan0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev br0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 default dev vlan0 proto kernel metric 256 mtu 1500 advmss 1440 default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 default dev br0 proto kernel metric 256 mtu 1500 advmss 1440 default dev vlan1 proto kernel metric 256 mtu 1500 advmss 1440 default dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 default via 2001:6f8:202:1b7::1 dev sixxs metric 1024 mtu 1280 advmss 1220

What's going wrong? What did I forget to do? I already tested AICCU on MacOSX and Ubuntu and didn't encountered such a problem. Thanks for any help Jeremy

Problems with OpenWRT

Jeroen Massar SixXS Staff

on Thursday, 14 June 2007 02:45:29

ip -6 addr add 2001:6f8:3cd::/64 dev br0

ip -6 route add 2001:6f8:3cd::/64 dev br0

This is wrong, for 2 reasons: - ::/64 == the first/lowest address in a subnet, as such that is an anycast prefix. Which you should never use. Use ::1/64 if you want an easily remembered number. (See IPv6 docs/google for more about "subnet anycast address") - the 'ip -6 ro add ...' is redundant, as you are already getting that /64 by configuring an address on the interface. You can see that in the route output you pasted which shows the route twice, which will never be fun for debugging, unless you know what you are doing of course. Next to that, how many 'default' routes do you require? Looking at the list you have 7. Most likely 6 of those are because you are using some broken Linux kernel, most likely a 2.4.x edition. for the rest of the problem, check further the "Reporting Problems" list on the contact page. Checking and making sure that the routing table is correct, then doing aiccu test, and doing tcpdumps to see which packets are actually flowing is the way to go. Also "Aiccu from backports" doesn't say a thing, which exact version is it? Use the latest if you want to be trouble free.

Problems with OpenWRT

Shadow Hawkins on Thursday, 14 June 2007 15:21:56

Well, I try to give all required information : AICCU version is aiccu_20070115

~$ aiccu test Tunnel Information for T11796: POP Id : bebru01 IPv6 Local : 2001:6f8:202:1b7::2/64 IPv6 Remote : 2001:6f8:202:1b7::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.102) ### 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: illegal option -- v BusyBox v1.4.0 (2007-02-24 00:35:56 EST) multi-call binary Usage: ping [OPTION]... host Send ICMP ECHO_REQUEST packets to network hosts Options: -c CNT Send only CNT pings -s SIZE Send SIZE data bytes in packets (default=56) -I IP Use IP as source address -q Quiet mode, only displays output at start and when finished ###### Did this work? [Y/n] ####### [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: illegal option -- v BusyBox v1.4.0 (2007-02-24 00:35:56 EST) multi-call binary Usage: ping [OPTION]... host Send ICMP ECHO_REQUEST packets to network hosts Options: -c CNT Send only CNT pings -s SIZE Send SIZE data bytes in packets (default=56) -I IP Use IP as source address -q Quiet mode, only displays output at start and when finished ###### Did this work? [Y/n] ####### [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 1.1.168.192.in-addr.arpa (192.168.1.1) 4.152 ms 4.126 ms 4.150 ms 2 1.28-65-87.adsl-dyn.isp.belgacom.be (87.65.28.1) 13.151 ms 13.354 ms 12.733 ms 3 5.237-201-80.adsl-static.isp.belgacom.be (80.201.237.5) 13.402 ms 15.638 ms 14.721 ms 4 ge1-0.intlmar1.isp.belgacom.be (194.78.0.147) 150.545 ms ge0-0.intlstr1.isp.belgacom.be (194.78.0.46) 16.840 ms ge0-0.intlmar1.isp.belgacom.be (194.78.0.47) 149.313 ms 5 fe1-0-0.br0.bnbru.be.easynet.net (194.53.172.96) 15.704 ms 15.731 ms 14.198 ms 6 ge1-3-0-100.br3.gdbru.be.easynet.net (212.100.162.87) 17.365 ms 18.188 ms 18.394 ms 7 fe0-0.ar1.gdbru.be.easynet.net (212.100.191.8) 16.832 ms 15.499 ms 16.412 ms 8 bebru01.sixxs.net (212.100.184.146) 16.866 ms 16.299 ms 18.400 ms ###### Did this work? [Y/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: icmp6_seq=0 ttl=64 time=0.8 ms 64 bytes from ::1: icmp6_seq=1 ttl=64 time=0.7 ms 64 bytes from ::1: icmp6_seq=2 ttl=64 time=0.7 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.7/0.7/0.8 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:202:1b7::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:202:1b7::2 (2001:6f8:202:1b7::2): 56 data bytes 64 bytes from 2001:6f8:202:1b7::2: icmp6_seq=0 ttl=64 time=0.8 ms 64 bytes from 2001:6f8:202:1b7::2: icmp6_seq=1 ttl=64 time=0.7 ms 64 bytes from 2001:6f8:202:1b7::2: icmp6_seq=2 ttl=64 time=0.7 ms --- 2001:6f8:202:1b7::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.7/0.7/0.8 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:202:1b7::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:1b7::1 (2001:6f8:202:1b7::1): 56 data bytes --- 2001:6f8:202:1b7::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ###### Did this work? [Y/n] n

~$ tcpdump -i vlan1 14:38:20.393780 IP 192.168.1.102.1033 > bebru01.sixxs.net.5072: UDP, length 152 14:38:21.386471 IP 192.168.1.102.1033 > bebru01.sixxs.net.5072: UDP, length 152 14:38:22.386467 IP 192.168.1.102.1033 > bebru01.sixxs.net.5072: UDP, length 152 14:38:23.386471 IP 192.168.1.102.1033 > bebru01.sixxs.net.5072: UDP, length 152

~$ tcpdump -i sixxs tcpdump: WARNING: arptype 65534 not supported by libpcap - falling back to cooked socket tcpdump: WARNING: sixxs: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on sixxs, link-type LINUX_SLL (Linux cooked), capture size 96 bytes 14:37:53.955771 IP6 fe80::2d0:b7ff:fea7:f184 > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28 14:38:20.392410 IP6 2001:6f8:202:1b7::2 > 2001:6f8:202:1b7::1: ICMP6, echo request, seq 0, length 64 14:38:21.385610 IP6 2001:6f8:202:1b7::2 > 2001:6f8:202:1b7::1: ICMP6, echo request, seq 1, length 64 14:38:22.385605 IP6 2001:6f8:202:1b7::2 > 2001:6f8:202:1b7::1: ICMP6, echo request, seq 2, length 64 14:38:23.385610 IP6 2001:6f8:202:1b7::2 > 2001:6f8:202:1b7::1: ICMP6, echo request, seq 3, length 64 14:38:24.385608 IP6 2001:6f8:202:1b7::2 > 2001:6f8:202:1b7::1: ICMP6, echo request, seq 4, length 64 14:39:58.963273 IP6 fe80::4f8:202:1b7:1 > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28

FirmwareOpenWrt White Russian - With X-Wrt Extensions 0.9 Kernel Linux 2.4.30 #1 Thu Feb 22 13:58:48 EST 2007 MAC 00:12:34:56:78:9A Device Linksys WRT54GS Board Broadcom BCM947XX

Without the two ip statements, I have :

2001:6f8:202:1b7::/64 dev sixxs metric 256 mtu 1280 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 fe80::/64 dev br0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan1 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 vlan0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev br0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 default dev vlan0 proto kernel metric 256 mtu 1500 advmss 1440 default dev br0 proto kernel metric 256 mtu 1500 advmss 1440 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 default dev vlan1 proto kernel metric 256 mtu 1500 advmss 1440 default dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 default via 2001:6f8:202:1b7::1 dev sixxs metric 1024 mtu 1280 advmss 1220 unreachable default dev lo proto none metric -1 error -128

I only need one route actually and as you guessed, I use a 2.4.x linux kernel. Will you say I can't go further with such a kernel version? :? I read Broadcom only provides a binary for 2.4.x |:( Maybe I have to find another device for my routing purposes... :'(

Problems with OpenWRT

Jeroen Massar SixXS Staff

on Thursday, 14 June 2007 18:25:14

Try installing DD-WRT which at least gives you a 2.4.34-pre2 kernel. Or: "ip -6 ro del default via dev X" and repeat for the non-sixxs interfaces. Also check 'ip -6 addr sho' to see which addresses are there, paste them here, then we can see if there is anything wrong with that. A number of people are happily using AYIYA on their wrt's so it does work.

Problems with OpenWRT

Shadow Hawkins on Thursday, 14 June 2007 19:41:16

I already tried DD-WRT wich didn't give me satisfaction : it is a fork of openwrt and the use of openwrt's package don't seem to be completely supported although it is needed for IPv6 and precisely for aiccu. Maybe I'll investigate more about it later as you say it could be of any help for me. So far, I deleted some -6 route defaults to have this result :

~$ ip -6 ro 2001:6f8:202:1b7::/64 dev sixxs metric 256 mtu 1280 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 fe80::/64 dev br0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan1 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 vlan0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev br0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 default dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 default via 2001:6f8:202:1b7::1 dev sixxs metric 1024 mtu 1280 advmss 1220

And then, as you asked me for :

~$ ip -6 addr sho 1: lo: <LOOPBACK,UP> inet6 ::1/128 scope host 2: eth0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> qlen 1000 inet6 fe80::212:17ff:fed4:40bc/64 scope link 3: eth1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> qlen 1000 inet6 fe80::212:17ff:fed4:40be/64 scope link 5: br0: <BROADCAST,MULTICAST,UP> inet6 fe80::212:17ff:fed4:40bc/64 scope link 6: vlan0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> inet6 fe80::212:17ff:fed4:40bc/64 scope link 7: vlan1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> qlen 5 inet6 fe80::212:17ff:fed4:40bc/64 scope link 8: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP> qlen 10 inet6 2001:6f8:202:1b7::2/64 scope global inet6 fe80::4f8:202:1b7:2/64 scope link

Problems with OpenWRT

Shadow Hawkins on Friday, 20 July 2007 19:29:31

Well, finally, I ran my own OpenWRT's build of the Kamikaze by including aiccu, ip, radvd, ... all stuff needed for IPv6. I just followed this for the build : http://forum.openwrt.org/viewtopic.php?pid=45838 It works great !! BUT ... Despite I was able to browse unfix.org and www.whatismyipv6.net to verify IPv6 was working, www.sixxs.net didn't work until I switched back to IPv4 by disabling IPv6 DNS. Then I tried a ping6 to see that :

jeremy@MBP2~$ ping6 -c5 whatismyipv6.net PING6(56=40+8+8 bytes) 2001:6f8:3cd::216:cbff:fe93:4a09 --> 2001:6f8:900:531::2 16 bytes from 2001:6f8:900:531::2, icmp_seq=0 hlim=50 time=70.124 ms 16 bytes from 2001:6f8:900:531::2, icmp_seq=1 hlim=50 time=70.219 ms 16 bytes from 2001:6f8:900:531::2, icmp_seq=2 hlim=50 time=68.308 ms 16 bytes from 2001:6f8:900:531::2, icmp_seq=3 hlim=50 time=71.422 ms 16 bytes from 2001:6f8:900:531::2, icmp_seq=4 hlim=50 time=67.435 ms --- whatismyipv6.net ping6 statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 67.435/69.502/71.422 ms jeremy@MBP2~$ ping6 -c5 unfix.org PING6(56=40+8+8 bytes) 2001:6f8:3cd::216:cbff:fe93:4a09 --> 2001:828:102:9::1:6:80 16 bytes from 2001:828:102:9::1:6:80, icmp_seq=0 hlim=49 time=39.101 ms 16 bytes from 2001:828:102:9::1:6:80, icmp_seq=1 hlim=49 time=36.769 ms 16 bytes from 2001:828:102:9::1:6:80, icmp_seq=2 hlim=49 time=36.445 ms 16 bytes from 2001:828:102:9::1:6:80, icmp_seq=3 hlim=49 time=38.283 ms 16 bytes from 2001:828:102:9::1:6:80, icmp_seq=4 hlim=49 time=37.304 ms --- unfix.org ping6 statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 36.445/37.580/39.101 ms jeremy@MBP2~$ ping6 -c5 www.sixxs.net PING6(56=40+8+8 bytes) 2001:6f8:3cd::216:cbff:fe93:4a09 --> 2001:838:1:1:210:dcff:fe20:7c7c --- noc.sixxs.net ping6 statistics --- 5 packets transmitted, 0 packets received, 100% packet loss

Maybe a bit disappointing...

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