|
OpenWRT: Automatic aiccu start problems
![[si]](/s/countries/si.gif) Shadow Hawkins on Tuesday, 09 November 2010 16:40:38
Short:
aiccu started from hotplug script, but IPv6 connection does not work.
Long:
I have OpenWRT 1.0 on my router using a PPPoE connection to internet.
I set up a script, /etc/hotplug.d/iface/20-aiccu-sixxs that starts and stops aiccu when the PPP connection is established or torn down.
Aiccu is started, the syslog shows (time is UTC):
Nov 7 17:54:45 (none) local7.info syslog: Succesfully retrieved tunnel information for TXXXX
Nov 7 17:54:45 (none) local7.info syslog: AICCU running as PID 1044
But, the sixxs device is not present, not even in ifconfig -a list.
If "aiccu stop" and "aiccu start" from interactive shell (over SSH), then everything just works. The syslog lines are the same as above.
I tried to set "verbose true" in aiccu.conf, but that generates a lot of logs (router has limited storage) and the problem did not happen in that case...
Any idea?
Regards,
David
OpenWRT: Automatic aiccu start problems
I set up a script, /etc/hotplug.d/iface/20-aiccu-sixxs that starts and stops aiccu when the PPP connection is established or torn down.
AICCU can just keep on running and running, it does not need to be restarted when a connection re-appears.
But, the sixxs device is not present, not even in ifconfig -a list.
In that case it was not properly setup. Is the daemon still running, are the paths to the binaries (especially 'ip') correct?
If "aiccu stop" and "aiccu start" from interactive shell (over SSH), then everything just works. The syslog lines are the same as above.
As you just have to start it once, what is the problem?
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Wednesday, 10 November 2010 15:40:56
The main reason to put the start in that place is the actual first start.
I can not start aiccu early during boot, since some needed resources are not available yet (mounted filesystems, ipv6 kernel module etc...)
I don't remember the exact steps I got to the current situation, because the router works OK most of the time. Every now and then the PPP connection drops or (even more rarely) the router reboots. Then after a while I check the IPv6 tunnel and notice it does (not) work.
So it was like a year or more ago, the I fist put the hotplug scripts in place.
Then weeks later I noticed they don't work correctly, so I added debug logging and various fixes/changes.
In that case it was not properly setup. Is the daemon still running, are the paths to the binaries (especially 'ip') correct? If by daemon you mean aiccu, then yes, it is (was) still running.
As for the path, the script sets LD_LIBRARY_PATH to the same value as in interactive shell. As for PATH, I will double check it.
Now I have 2 choices:
- leave only a single startup script to start aiccu ( /etc/init.d/S70aiccu - it might also have PATH problems, *bin/ip is on external storage that is not mounted right on boot, the ipv6 kernel module is also there )
- check the PATH in the iface hotplug script
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Thursday, 23 December 2010 16:49:40AICCU can just keep on running and running, it does not need to be restarted when a connection re-appears.
If I start it before I get internet connectivity, it aborts.
That is why I put it in the iface up/down scripts.
Here is the log:
local7.err syslog: Couldn't resolve host tic.sixxs.net, service 3874
local7.err syslog: Couldn't connect to the TIC server tic.sixxs.net
local7.err syslog: Couldn't retrieve first tunnel for the above reason, aborting
Is there a setting to make aiccu not exit, but keep retrying?
Regards,
David
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Monday, 07 February 2011 15:50:51
Same thing happened again.
Router boots, aiicu starts, but exits with the above log entry as the network connection is not running yet.
I'll put it back into the iface hotplug script.
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Saturday, 19 February 2011 19:08:45
I had a network outage (ISP upstream cable cut).
After connection came back, I noticed I have no IPv6 connectivity.
It is similar as in my first post.
The gist of it is:
- everything works
- IPv4 drops (pppd disconnects and tries to reconnect, succeeding after a couple of hours)
- IPv4 works again
- IPv6 does not work
aiccu was started automatically when IPv4 came back.
The log is normal:
Feb 16 10:11:03 (none) local7.info syslog: Succesfully retrieved tunnel information for T14647
Feb 16 10:11:03 (none) local7.info syslog: AICCU running as PID 9005
Again the main problem is, that there is not "sixxs" device in the output of ifconfig.
I no other suggestion, I'll just restart aiicu (that worked last time).
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Sunday, 20 February 2011 19:07:49I no other suggestion, I'll just restart aiicu (that worked last time).
I did "aiccu stop" followed by "aiccu start" and it works now, as expected.
After "aiccu stop" the sixxs device is gone:
# ifconfig sixxs
ifconfig: sixxs: error fetching interface information: Device not found
After starting aiccu it re-appeears.
Any idea why it would not appear on start of aiccu and why aiccu doesn't complain about it?
OpenWRT: Automatic aiccu start problems
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 05 March 2011 11:35:09
Hi David,
make sure the following modules are loaded before the aiccu service is going to be started:
ipv6
tun
tunnel4
sit
it depends on you OpenWRT version where the module loading order has to be defined. On Backfire and the Bleeding Edge trunk it's defined in /etc/modules.d:
20-ipv6
30-tun
31-iptunnel4 (contains the module tunnel4)
32-sit
Your OpenWRT version may have the file /etc/modules then you can append the above mentioned modules the and they will be loaded before any service is going to start. The next possibility is to add the module loading command to either /etc/init.d/rcS, a new created startup script with a lower sting no or integrating the module loading commands to the aiccu startup script:
/sbin/insmod /sbin/insmod /lib/modules/2.6.37.1/ipv6.ko
/sbin/insmod /sbin/insmod /lib/modules/2.6.37.1/tun.ko
/sbin/insmod /sbin/insmod /lib/modules/2.6.37.1/tunnel4.ko
/sbin/insmod /sbin/insmod /lib/modules/2.6.37.1/sit.ko
replace 2.6.37.1 with you kernel version !!
good luck
with best regards from still could Berlin
Olaf
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Friday, 15 April 2011 21:56:46
I discovered something.
Again, my router was restarted and the SixXS tunnel was not working.
If I stop aiccu and restart it, it works.
The thing is: If I am missing a few directories in the PATH, I can reproduce the problem.
Those directories are extra bins on my USB stick. They contain among others the 'ip' program.
I guess it is a requirement for aiccu, is it?
Strangely, it does not complain in logs or stdour/err.
I fixed the PATH in the startup script, so I guess the problem is solved. (we will see the next time the router is restarted).
David
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Friday, 15 April 2011 21:58:41
I see Jeroen mentioned 'ip' above...
I browsed around the SixXS pages and I could not find a requirements list for aiccu.
OpenWRT: Automatic aiccu start problems
ip (also called iproute2) is effectively a base requirement for any Linux distro, that is why it is not listed anywhere. If you had a proper package, eg like the Debian packages, then you would have a dependency for it though.
OpenWRT: Automatic aiccu start problems
Shadow Hawkins on Sunday, 24 April 2011 00:27:21
Yes, but I have OpenWRT.
Also , 'ip' is a requirement on recent distros, older ones are ifconfig/route based.
OpenWRT: Automatic aiccu start problems
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 24 March 2011 05:24:59
Just a side note, but I think you started aiccu too early - generally it should be started after radvd and rdate.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 09 November 2010 16:54:06
Posting is only allowed when you are