SixXS::Sunset 2017-06-06

No support for AICCU post-up scripts under Linux?
[us] Shadow Hawkins on Thursday, 10 September 2009 09:50:13
I need to change some settings once AICCU is started and there is a valid IPv6 address from SixXS. However, I can't find an easy way to make this happen, and any help would be appreciated. Forum setup-557641 states that the "setupscript" option in "/etc/aiccu.conf" is only available under Windows, and is recently confirmed at Debian #538129. Another option mentioned was to just include the necessary commands in "/etc/init.d/aiccu", after the "start-stop-daemon" command in the "start" section. However, at this point, the "sixxs" interface exists but doesn't have any addresses assigned to it yet. Finally, aiccu doesn't appear to make use of "ifup", so any scripts put in "/etc/network/if-up.d" aren't even executed. Is there anything else I can try? Otherwise, I'll probably end up starting a script from "/etc/init.d/aiccu", then doing a loop with a sleep statement until an IP address is found on the interface, after which any other necessary scripts can be run. (I should probably just call run-parts to "/etc/network/if-up.d" with the appropriate arguments.) Thanks!
No support for AICCU post-up scripts under Linux?
[ch] Jeroen Massar SixXS Staff on Thursday, 10 September 2009 09:54:59
The 'setupscript' option is currently not available. When I have time I will be repacking the new edition I have been working on, this one will support that. 'Downstream' distributions (eg Debian,Redhat etc) are really bad in forwarding problem reports and bug fixes upstream (unless you google for them yourself every once in a while) and fixes tend to be applied with a GPL license even though the license for aiccu is BSD, thus they can't be taken over anyway.
Finally, aiccu doesn't appear to make use of "ifup", so any scripts put in
"/etc/network/if-up.d" aren't even executed.
That is a mechanism of your distribution, and afaik, those are called by the udev scripts when the interface comes up, this should in theory actually work. The big question is: what do you need to change that might be related to the tunnel interface?
No support for AICCU post-up scripts under Linux?
[us] Shadow Hawkins on Thursday, 10 September 2009 16:16:04
I will look into the udev scripts more, and see if I can't find a workable solution there, pending your new edition. In terms of changes: First, I need to re-run my iptables firewall script. Second, I want to assign a subnet IP to the interface in addition to the tunnel IP, so that outgoing connections from the router itself have a subnet IP as the source address, rather than the tunnel IP. (This can partially be accomplished through editing /etc/gai.conf, but requires the subnet address to also be added to the sixxs interface, otherwise the earlier RFC 3484 rule #5 has already chosen the tunnel address.)
No support for AICCU post-up scripts under Linux?
[us] Shadow Hawkins on Thursday, 10 September 2009 22:39:01
I got the if-up scripts working. The "sixxs" interface just needed to be defined in "/etc/network/interfaces" ("iface sixxs inet manual" was sufficient), and "auto sixxs" (same as "allow-hotplug sixxs") is also necessary for the if-up/down scripts to be executed. However, even at this point, I found that the interface was not yet "fully configured" and was lacking the global IPv6 tunnel address. Please consider this as you implement "setupscript", so that it executes only after the interface is "fully configured" and has the IPv6 tunnel address assigned. In the meantime, I was able to accomplish my original goal by just defining the interface in "/etc/network/interfaces" as "iface sixxs inet6 static" and giving it the desired subnet address. Once AICCU runs, the tunnel address is added - and fortunately, my configured subnet address remains.

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker