Hi everybody I have observed erratic startup behaviour with Bering possibly related to DHCP.
Network interfaces are started by the ifup -a command in /etc/init.d/networking. Ifup is a binary I have not been able to find the source for, maybe someone can point me to a link.... Nevertheless, it is often the case that the external interface of a LEAF box gets its external address using DHCP which is spawned from ifup, thus becoming a process on its own. The timing behaviour of the DHCP client cannot be predicted, so it is possible that even though the interface is up, the gateway and IP addresses have not yet been set. This may cause problems with subsequent initialisation of FreeS/Wan and shorewall, as both depend on the completely initialised interface, e.g. IP and (often) default gateway address. I believe we need to introduce a mechanism to detect the completed initialisation of a given interface _before_ init may continue. I used such a mechanism some time ago when I was running Bering on a PCMCIA only box, PCMCIA NICS being inherently slow at init. This code is probably not suitable in this case as it does not check for the presence of a default route nor a correctly set IP address. Thoughts Erich THINK P�ntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
