OpenWrt Forum Archive

Topic: AICCU - IPv6

The content of this topic has been archived on 13 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
mcfly9
2 Jun 2007, 12:54

Hello,

I am trying to get aiccu working. I was following the IPv6 howto on the wiki site, but cannot get it working.

I managed to install AICCU, configured it and it seems it is working OK:

root@OpenWrt:/etc/modules.d# aiccu test
Tunnel Information for T<tunnelnumber>:
POP Id      : simbx01
IPv6 Local  : 2001:<***>:c9::2/64
IPv6 Remote : 2001:<***>:c9::1/64
Tunnel Type : ayiya
Adminstate  : enabled
Userstate   : enabled

Now how should I continue?

I don't see a tunnel interface in ifconfig. I guess that would be the next thing to do, but I'm puzzled how to continue...

Any ideas?

UPDATE:

I see now this in logread:

Jun  2 12:22:05 OpenWrt local7.err syslog: [tun-start] Couldn't open device /dev/net/tun: No such file or directory (2)

I am using the latest Kamikaze.

UPDATE 2:

ipkg install kmod-tun

did the trick...

(Last edited by mcfly9 on 2 Jun 2007, 13:31)

Post #2
Cisien
2 Jun 2007, 16:14

do you have the ipv6 modules loaded, what is your ifconfig -a output? (and lsmod)

Post #3
mcfly9
2 Jun 2007, 16:34

Meanwhile I figured it out... For some reason I need to insmod ipv6 after every boot.

Apart from that, everything works like a charm. I have now IPv6 access on all my computers smile

Post #4
cereal
3 Jun 2007, 02:06

create a file /etc/modules.d/25-ipv6 and write "ipv6" into that file. on the next bootup the ipv6-module will be loaded automatical.

Post #6
forum2006
3 Jun 2007, 13:32
mtp wrote:

I moved to Kamikaze today and there does not seem be a package for it anymore. I use http://downloads.openwrt.org/kamikaze/7 … 4/packages as a source for my packages.

at this location there are only a base set of packages.

if you like more packages you have to build them by yourself using the sdk or the build-system. i recommend the build-system.

Post #7
mcfly9
3 Jun 2007, 13:48

I simply used the aiccu package from the whiterussian rc6 release... don't know if this may cause any problems, it works like a charm for me.

Post #8
forum2006
3 Jun 2007, 13:49

now you now, where all your problems are coming from smile

(Last edited by forum2006 on 3 Jun 2007, 13:49)

Post #9
mcfly9
3 Jun 2007, 14:18

Well, I understand the risks using the not-so ported versions smile Anyway, got it working, that's the most important wink

Post #10
jeremy.s
19 Jun 2007, 21:51
mcfly9 wrote:

I simply used the aiccu package from the whiterussian rc6 release... don't know if this may cause any problems, it works like a charm for me.

Don't seem to work like a charm for me ...

Jun 19 21:10:17 OpenWrt local7.debug syslog: sock_getline() : "400 Deprecated Client Detected, please upgrade to the newest version which can be found at http://www.sixxs.net/tools/aiccu/" 
Jun 19 21:10:17 OpenWrt local7.err syslog: Couldn't pass client information: Deprecated Client Detected, please upgrade to the newest version which can be found at http://www.sixxs.net/tools/aiccu/. 
Jun 19 21:10:17 OpenWrt local7.err syslog: Couldn't retrieve first tunnel for the above reason, aborting

Then I installed the version 2007.01.15 :

Succesfully retrieved tunnel information for Txxxxx
sock_printf()  : "QUIT Tschau!"
Tunnel Information for Txxxxx:
POP Id      : bebru01
IPv6 Local  : 2001:...::2/64
IPv6 Remote : 2001:...::1/64
Tunnel Type : ayiya
Adminstate  : enabled
Userstate   : enabled
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started

Then I tried to ping6 IPv6 Local => OK
Then I tried to ping6 IPv6 Remote => KO!!!

So I tcpdumped on sixxs and eth0.1 interfaces to see something like :

~$ tcpdump -i sixxs
22:28:45.061533 IP6 2001:...::2 > 2001:...::1: ICMP6, echo request, seq 5, length 64

~$ tcpdump -i eth0.1
22:28:45.062390 IP 192.168.5.2.1038 > bebru01.sixxs.net.5072: UDP, length 152

Where 192.168.5.2 is, of course, the WAN interface of the router

For information, I run the last kamikaze found on x-wrt website wich is on based kernel 2.4.34
I also ran these :

~$ ip -6 addr sho
1: lo: <LOOPBACK,UP> 
    inet6 ::1/128 scope host 
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP> qlen 1000
    inet6 fe80::212:17ff:fed4:40bc/64 scope link 
3: eth0.0: <BROADCAST,MULTICAST,PROMISC,UP> 
    inet6 fe80::212:17ff:fed4:40bc/64 scope link 
4: eth0.1: <BROADCAST,MULTICAST,PROMISC,UP> 
    inet6 fe80::212:17ff:fed4:40bc/64 scope link 
5: br-lan: <BROADCAST,MULTICAST,UP> 
    inet6 fe80::212:17ff:fed4:40bc/64 scope link 
6: wl0: <BROADCAST,MULTICAST,PROMISC,UP> qlen 1000
    inet6 fe80::212:17ff:fed4:40be/64 scope link 
15: sixxs: <POINTOPOINT,MULTICAST,NOARP,PROMISC,UP> qlen 10
    inet6 2001:...::2/64 scope global 
    inet6 fe80::4f8:202:1b7:2/64 scope link 

~$ ip -6 route sho
2001:...::/64 dev sixxs  metric 256  mtu 1280 advmss 1220
fe80::/64 dev eth0  metric 256  mtu 1500 advmss 1440
fe80::/64 dev br-lan  metric 256  mtu 1500 advmss 1440
fe80::/64 dev wl0  metric 256  mtu 1500 advmss 1440
fe80::/64 dev eth0.0  metric 256  mtu 1500 advmss 1440
fe80::/64 dev eth0.1  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 br-lan  metric 256  mtu 1500 advmss 1440
ff00::/8 dev wl0  metric 256  mtu 1500 advmss 1440
ff00::/8 dev eth0.0  metric 256  mtu 1500 advmss 1440
ff00::/8 dev eth0.1  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
unreachable default dev lo  proto none  metric -1  error -128

What can I do? It seems to be a route problem but I don't know wich one... (well, I don't know what look a good route config should have)
Could it be due to kernel version?
Any advice is welcome wink

Post #11
mcfly9
20 Jun 2007, 22:11
jeremy.s wrote:
mcfly9 wrote:

I simply used the aiccu package from the whiterussian rc6 release... don't know if this may cause any problems, it works like a charm for me.

Don't seem to work like a charm for me ...

I actually didn't use the WAN connection but simply used a default gateway to go out to the net. Don't know how much this changes...


Answering your question where the problem might be is I think in deed the routing. I only vaguely remember how my routing table looked like (briecked my test router smile ), and think that I had to remove the unreachable route to get it working... but I'm not sure any more, sorry...

The discussion might have continued from here.