Forum - Aiccu on Fritzbox with Freetz :: SixXS - IPv6 Deployment & Tunnel Broker

Aiccu on Fritzbox with Freetz

Shadow Hawkins on Friday, 24 September 2010 22:45:20

I want to use aiccu on my Fritzbox 7270. I installed aiccu and got it running but autotest produces the following:

ip: SIOCADDTUNNEL: No buffer space available ip: RTNETLINK answers: File exists ip: RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.4.1) ### 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.4.1 (192.168.4.1): 56 data bytes 64 bytes from 192.168.4.1: seq=0 ttl=64 time=0.666 ms 64 bytes from 192.168.4.1: seq=1 ttl=64 time=0.421 ms 64 bytes from 192.168.4.1: seq=2 ttl=64 time=0.929 ms --- 192.168.4.1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.421/0.672/0.929 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (78.35.24.124) ### 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 78.35.24.124 (78.35.24.124): 56 data bytes 64 bytes from 78.35.24.124: seq=0 ttl=58 time=45.550 ms 64 bytes from 78.35.24.124: seq=1 ttl=58 time=22.314 ms 64 bytes from 78.35.24.124: seq=2 ttl=58 time=24.423 ms --- 78.35.24.124 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 22.314/30.762/45.550 ms ###### ####### [3/8] Traceroute to the PoP (78.35.24.124) 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 78.35.24.124 (78.35.24.124), 30 hops max, 38 byte packets 1 rdsl-koln-de02.nw.mediaways.net (213.20.58.131) 50.780 ms 37.892 ms 36.63 5 ms 2 xmwc-koln-de02-chan-20.nw.mediaways.net (195.71.204.78) 26.507 ms 21.154 m s 24.251 ms 3 rmwc-koln-de01-gigaet-0-1-0.nw.mediaways.net (62.53.198.161) 20.967 ms 48. 901 ms 20.414 ms 4 195.71.248.54 (195.71.248.54) 21.204 ms 43.291 ms 23.487 ms 5 core-pg2-t91.netcologne.de (87.79.16.109) 20.888 ms 20.325 ms 20.574 ms 6 core-eup2-t42.netcologne.de (87.79.16.213) 20.292 ms 21.383 ms 21.025 ms 7 sixxs-pop1.netcologne.net (78.35.24.124) 22.016 ms 25.105 ms 20.377 ms ###### ###### [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: seq=0 ttl=64 time=0.437 ms 64 bytes from ::1: seq=1 ttl=64 time=0.684 ms 64 bytes from ::1: seq=2 ttl=64 time=0.865 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.437/0.662/0.865 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4dd0:ff00:30e::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4dd0:ff00:30e::2 (2001:4dd0:ff00:30e::2): 56 data bytes --- 2001:4dd0:ff00:30e::2 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4dd0:ff00:30e::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:4dd0:ff00:30e::1 (2001:4dd0:ff00:30e::1): 56 data bytes --- 2001:4dd0:ff00:30e::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% 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. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:4dd0:ff00:30e::2, 30 hops max, 16 byte packets 1 ###### ###### [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 traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:4dd0:ff00:30e::2, 30 hops max, 16 byte packets 1 ###### ###### 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.

ifconfig:

adsl Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:2000 Metric:1 RX packets:2859838 errors:0 dropped:0 overruns:0 frame:0 TX packets:1687745 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:3988605756 (3.7 GiB) TX bytes:230859147 (220.1 MiB) ath0 Link encap:Ethernet HWaddr 00:1F:3F:D5:2B:42 UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:2290 Metric:1 RX packets:121373 errors:0 dropped:0 overruns:0 frame:0 TX packets:231671 errors:0 dropped:58 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8750461 (8.3 MiB) TX bytes:337593380 (321.9 MiB) cpmac0 Link encap:Ethernet HWaddr 00:1F:3F:F0:16:C7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1544213 errors:0 dropped:0 overruns:0 frame:0 TX packets:2573945 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:189930595 (181.1 MiB) TX bytes:3580265547 (3.3 GiB) dsl Link encap:Point-to-Point Protocol inet addr:192.168.4.1 P-t-P:192.168.4.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:336000 errors:0 dropped:0 overruns:0 frame:0 TX packets:253368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:348916476 (332.7 MiB) TX bytes:105234510 (100.3 MiB) eth0 Link encap:Ethernet HWaddr 00:1F:3F:F0:16:C7 UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:1544213 errors:0 dropped:0 overruns:0 frame:0 TX packets:100700 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:128 RX bytes:189930595 (181.1 MiB) TX bytes:60267359 (57.4 MiB) guest Link encap:Ethernet HWaddr 00:1F:3F:F0:16:C7 inet addr:192.168.179.1 Bcast:192.168.179.255 Mask:255.255.255.0 UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:121 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:6098 (5.9 KiB) lan Link encap:Ethernet HWaddr 00:1F:3F:F0:16:C7 inet addr:192.168.4.1 Bcast:192.168.7.255 Mask:255.255.248.0 UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:1675534 errors:0 dropped:0 overruns:0 frame:0 TX packets:299084 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:170729548 (162.8 MiB) TX bytes:345835826 (329.8 MiB) lan:0 Link encap:Ethernet HWaddr 00:1F:3F:F0:16:C7 inet addr:169.254.1.1 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1085 errors:0 dropped:0 overruns:0 frame:0 TX packets:1085 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:97694 (95.4 KiB) TX bytes:97694 (95.4 KiB) sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:xxxx:xxxx:xxxx::2/64 Scope:Global inet6 addr: fe80::a9fe:101/64 Scope:Link inet6 addr: fe80::c0a8:b301/64 Scope:Link inet6 addr: fe80::c0a8:401/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wifi0 Link encap:Ethernet HWaddr 00:1F:3F:D5:2B:42 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:260216 errors:0 dropped:0 overruns:0 frame:20244 TX packets:231800 errors:20 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:33980886 (32.4 MiB) TX bytes:346380626 (330.3 MiB) Interrupt:80 Memory:c03e0000-c03f0000

On my notebook with Ubuntu aiccu and ipv6 is running fine, but I need it on the router. Can anyone help? I will be happy to post more information about the setup.

Aiccu on Fritzbox with Freetz

Jeroen Massar SixXS Staff

on Friday, 24 September 2010 23:28:34

Assuming that freetz is just another Linux, what are the 'adsl' and 'dsl' interfaces for and what is really below them? Also it does not seem like you have a single public IP address on that thing as everything is RFC1918. Your tunnel "sixxs Link encap:IPv6-in-IPv4" looks like a protocol-41 tunnel, but with the combination of RFC1918 which implies NAT how do the packets want to go to the PoP. Next to that the tunnel interface has three link locals which re-enforces that you have multiple IP addresses, thus the question there becomes: what is the local address? The following would be useful here: - uname -a - ip link sho - ip addr sho - ip ro sho - ip -6 ro sho - iptables -v --list -n --line-numbers - ip6tables -v --list -n --line-numbers (indeed 'ip' is inconsistent, 'ip addr sho' shows both IPv4 and IPv6, while "ip ro sho" only shows IPv4...) Also note that you should only run one instance of AICCU at the same time, you can't run multiple of them.

ip: SIOCADDTUNNEL: No buffer space available

Indicates a kernel issue generally though which only can be fixed with reboots.

Aiccu on Fritzbox with Freetz

Shadow Hawkins on Friday, 24 September 2010 23:51:34

- uname -a

Linux fritz.fonwlan.box 2.6.19.2 #3 Tue Sep 7 16:08:51 CEST 2010 mips GNU/Linux

- ip link sho

1: cpmac0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff 2: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 3: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 128 link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff 5: lan: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc noqueue link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff 6: guest: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc noqueue link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff 19: wifi0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:1f:3f:d5:2b:42 brd ff:ff:ff:ff:ff:ff 22: ath0: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 2290 qdisc pfifo_fast qlen 1000 link/ether 00:1f:3f:d5:2b:42 brd ff:ff:ff:ff:ff:ff 27: dsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 100 link/ppp 28: adsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 2000 qdisc tbf qlen 32 link/[19] 37: sixxs@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue link/sit 192.168.4.1 peer 78.35.24.124

- ip addr sho

1: cpmac0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff 2: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 128 link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff 5: lan: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc noqueue link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff inet 192.168.4.1/21 brd 192.168.7.255 scope global lan inet 169.254.1.1/16 brd 169.254.255.255 scope global lan:0 6: guest: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 1500 qdisc noqueue link/ether 00:1f:3f:f0:16:c7 brd ff:ff:ff:ff:ff:ff inet 192.168.179.1/24 brd 192.168.179.255 scope global guest 19: wifi0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:1f:3f:d5:2b:42 brd ff:ff:ff:ff:ff:ff 22: ath0: <BROADCAST,MULTICAST,UP,LOWER_UP200> mtu 2290 qdisc pfifo_fast qlen 1000 link/ether 00:1f:3f:d5:2b:42 brd ff:ff:ff:ff:ff:ff 27: dsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP200> mtu 1500 qdisc pfifo_fast qlen 100 link/ppp inet 192.168.4.1/32 scope global dsl 28: adsl: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 2000 qdisc tbf qlen 32 link/[19] 37: sixxs@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue link/sit 192.168.4.1 peer 78.35.24.124 inet6 2001:4dd0:ff00:30e::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c0a8:b301/64 scope link valid_lft forever preferred_lft forever inet6 fe80::a9fe:101/64 scope link valid_lft forever preferred_lft forever inet6 fe80::c0a8:401/64 scope link valid_lft forever preferred_lft forever

- ip ro sho

192.168.180.1 dev dsl metric 2 192.168.180.2 dev dsl metric 2 93.129.127.141 dev dsl metric 3 93.129.119.124 dev dsl metric 2 192.168.179.0/24 dev guest src 192.168.179.1 192.168.0.0/21 dev lan src 192.168.4.1 169.254.0.0/16 dev lan src 169.254.1.1 default dev dsl metric 2

- ip -6 ro sho

2001:xxxx:xxxx:30e::/64 via :: dev sixxs metric 256 expires 42949387sec fe80::/64 via :: dev sixxs metric 256 expires 42949387sec ff00::/8 dev sixxs metric 256 expires 42949387sec default via 2001:xxxx:xxxx:30e::1 dev sixxs metric 1024 expires 42949387sec

- iptables -v --list -n --line-numbers

Chain INPUT (policy ACCEPT 3660 packets, 401K bytes) num pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 11167 packets, 5115K bytes) num pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 4414 packets, 662K bytes) num pkts bytes target prot opt in out source destination

- ip6tables -v --list -n --line-numbers

ip6tables v1.4.1.1: can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?) Perhaps ip6tables or your kernel needs to be upgraded.

Do i need to setup ip6tables in order for aiccu to work? Wasn't so on my laptop...

Aiccu on Fritzbox with Freetz

Jeroen Massar SixXS Staff

on Saturday, 25 September 2010 00:03:23

37: sixxs@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue

link/sit 192.168.4.1 peer 78.35.24.124

That won't (easily) work, as the local portion is RFC1918 and thus you need to tweak the NAT box to send protocol 41 packets your way. Better convert it to an AYIYA tunnel and use that saves a lot of headaches.

default via 2001:xxxx:xxxx:30e::1 dev sixxs metric 1024 expires 42949387sec

As you have a 2.6.19 kernel which is close to ancient you might want to try adding a 'ip -6 ro add 2000::/3 via 2001:4dd0:ff00:30e::1'. Why did you 'xxx' out the addresses btw, they are there in other places and anyway they are published through whois too. It seems also that this '192.168.4.1' address is on the 'lan' and 'dsl' interface this while your routing table also has:

93.129.127.141 dev dsl metric 3

93.129.119.124 dev dsl metric 2

I think you should first fix your IPv4 connectivity (removing the 192.168.4.1 from dsl might be a good start) , most likely you do have a public IPv4 address on that interface and suddenly (after changing the local part of the tunnel) things could work.

default dev dsl metric 2

Unless 'dsl' is a PtP tunnel, that is a rather weird setup that would need a gateway.

Do i need to setup ip6tables in order for aiccu to work? Wasn't so on my laptop...

You don't, but it is always good to check if policy is not blocking any packets on their way out.

Aiccu on Fritzbox with Freetz

Shadow Hawkins on Saturday, 25 September 2010 00:14:08

The xxxes where nonesense. :) Your point. I think 'dsl' is the gateway to the WAN for the LAN-users and 'lan' ist the device connecting the Router to the LAN. But this is merely guessing. The Fritzbox is a Router and DSLModem in one btw with a PPPoE connection to the ISP. I fear removing the adress of dsl would cut off all LAN users from the web. And even if would like to do so, dunno how... Thks for advice so far!

Aiccu on Fritzbox with Freetz

Shadow Hawkins on Monday, 27 September 2010 09:09:24

Why don't you use the built in SIXXS-Support in the newest firmware (xx.04.86 from 17.09.2010)? It is easy to setup and works fine. And for the advantages of freetz, you can use the actual freetz-trunk. It is supporting the new firmware by defult. greetz

Aiccu on Fritzbox with Freetz

Shadow Hawkins on Monday, 27 September 2010 10:39:51

This works only if you have got a subnet, but I lack 5 points to request one...

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