Forum - AICCU on Synology :: SixXS - IPv6 Deployment & Tunnel Broker

AICCU on Synology

Shadow Hawkins on Sunday, 09 December 2012 14:02:08

Hey. I've tried to install AICCU on my Synology NAS DS213 using this wiki page. It all goes well, I've gotten IPv6 connectivity:

DiskStation> aiccu start Tunnel Information for Txxxxx: POP Id : nlams05 IPv6 Local : 2001:610:600:63a::2/64 IPv6 Remote : 2001:610:600:63a::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled DiskStation> ping6 ipv6.google.com PING ipv6.google.com (2a00:1450:400c:c05::93): 56 data bytes 64 bytes from 2a00:1450:400c:c05::93: seq=0 ttl=55 time=17.772 ms 64 bytes from 2a00:1450:400c:c05::93: seq=1 ttl=55 time=19.435 ms 64 bytes from 2a00:1450:400c:c05::93: seq=2 ttl=54 time=18.131 ms 64 bytes from 2a00:1450:400c:c05::93: seq=3 ttl=56 time=17.687 ms 64 bytes from 2a00:1450:400c:c05::93: seq=4 ttl=55 time=21.259 ms ^C --- ipv6.google.com ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 17.687/18.856/21.259 ms

But when I reboot my NAS and try again, for some reason AICCU doesn't start.

DiskStation> ping6 ipv6.google.com PING ipv6.google.com (2a00:1450:400c:c05::93): 56 data bytes ping6: sendto: Network is unreachable

I have followed the "Automating the whole thing" section, but it still doesn't function. Using some information from Google, I've also tried editting the /etc/rc.local file:

#!/bin/sh # Optware setup [ -x /etc/rc.optware ] && /etc/rc.optware start echo "1" > /proc/sys/net/ipv6/conf/all/forwarding insmod /usr/lib/modules/tun.ko aiccu start ip a add 2001:610:600::/48 dev eth0 exit 0

But that didn't work either. Finally I tried putting all commands in a script file, chmod +x that and put it in /usr/syno/etc/rc.d/S99aiccu.sh, but that doesn't work either. Does anybody have an idea why AICCU doesn't start automatically when I start my NAS? Thanks in advance!

AICCU on Synology

Jeroen Massar SixXS Staff

on Sunday, 09 December 2012 14:32:33

But when I reboot my NAS and try again, for some reason AICCU doesn't start.

Check your logs that will likely explain what goes wrong, which is likely time and/or network connectivity related.

ip a add 2001:610:600::/48 dev eth0

While almost correct, this will not do what you want it to do. You will want to null-route the prefix with:

ip -6 route add 2001:610:600::/48 dev lo

and then put an address on the interface with:

ip -6 addr add 2001:610:600::1/64 dev eth0

Note, only a single /64, as that is what Router Advertisements use.

AICCU on Synology

Shadow Hawkins on Sunday, 09 December 2012 16:08:54

Thanks for your reply. I've done some more research and found this in the /var/log/messages file:

Dec 9 17:02:31 aiccu: TIC Server does not support TLS but TLS is not required, continuing Dec 9 17:02:34 aiccu: Already running instance HUP'ed, exiting

So it seems that Aiccu is already running, but for some reason doesn't work as intended...

AICCU on Synology

Jeroen Massar SixXS Staff

on Monday, 10 December 2012 11:46:00

Dec 9 17:02:31 aiccu: TIC Server does not support TLS but TLS is not required, continuing

That is normal, it also states: continuing

Dec 9 17:02:34 aiccu: Already running instance HUP'ed, exiting

How are you starting AICCU, are you maybe starting multiple copies at the same time?

So it seems that Aiccu is already running, but for some reason doesn't work as intended...

Try 'ps aux' to see if that is really the case. As stated on the contact page, try running AICCU in verbose mode with daemonize false, that should provide the log messages directly instead of having to figure out where they go to (/var/log/messages and friends)

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