I may be mistaken but I think ubuntu doesn't start the network
interfaces until a user has logged on and the network manager
applet is running.
Actually, if you turn off the windows-ish quiet boot even leaving the
silly splash screen on, you will see that the network elements are
initialized (to some degree) long before the user is able to log in.
And lets distinguish between the NM applet which is ONLY used after
there is a GUI to work in and the software that actually manages the
interfaces.
Sorry my wording was bad there, yes the NetworkManager daemon does start
at boot and waits for the users NM applet to give instructions if you will.
I gave 2 options there, one was to continue what you were/are doing the other would be to move away from NM and have a debian 4.0 style configuration.I am sorry, that sounds like I think I know what I am doing here when actually I am poking and praying. But this part at least I KNOW that some of it is done before a user is even allowed to log in.I found this https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/392826 via a quick google search so the answer to your question about reordering the script doesn't seem like it would work.Good find. Thanks. The problem I first see is that that user moved his DHCP server to S99 but there are services starting before that that might then not be able to run so he may have caused his own continued failure. I really do not know.I believe you would have to switch your network preferences away from networkmanager back to the older /etc/network/interfaces method or restart the dhcp server after you have logged in and the networkmanager applet has started as you've been doing.Perhaps, that would be Craig's opinion too. I just think it should not be necessary because I CAN start the DHCP server while NM/-applet is running and it works.
to accomplish this sudo aptitude purge network-manager network-manager-gnome then add these lines to /etc/network/interfaces auto eth0 iface eth0 inet static address 192.168.1.100 netmask 255.255.255.0 gateway 192.168.1.1 replace options as necessary, close and save. then run /etc/init.d/network restartYou might also need to create a symlink to /etc/rc2.d/ for /etc/init.d/networking that starts before your dhcp server does.
<<attachment: ryan.vcf>>
_______________________________________________ PLUG-applications mailing list [email protected] http://lists.plug.phoenix.az.us/cgi-bin/mailman/listinfo/plug-applications Reminder: All replies will go back to this mailing list. If you wish to send a reply to a specific person, please use the reply function and change the "To:" address to that person before sending.
