On Sat, Apr 03, 2004 at 11:31:39PM +1000, Eddie F wrote: > >> > > After first boot settings entered for eth0 where lost. Sorted > >> > > all this out and all works fine after running ifup eth0, but > >> > > this interface isn't started at boot. So... How does Debian > >> > > 3.0 r2 normally start network interfaces at bootup? > >> > > >> >In /etc/network/interfaces. > >> > >> Ummm... yeh... I've edited this apropriately, so when I bring up the > >> interface manually it works ok... But how does Debian start the > >> interfaces at boot, so I don't have to running ifup eth0, everytime I > >> boot? > > > >Define "appropriately"... > > Definition = Copied from a latop on the same network, except with different > IP :-)
In the case of the laptop, I'm guessing that it's a PCMCIA card, so the interface is being brought up by the pcmcia-cs package. > # /etc/network/interfaces -- blah blah > # The loopback interface > auto lo The auto line tells the networking init script to bring up an interface. You need to add "auto eth0" > >Make sure that "network" in /etc/rc2.d/ is actually starting. > > Did this (I think) by creating the sym' link; > S40networking -> ../init.d/networking > Hope this is right... got this frm finding same in rcS.d The rcS.d one is all you need. The one you added can happily be removed again. :-) > Anyway seems to be starting, as I get the mesage at boot; > Configuring network interfaces: ifup : interface lo already configured > done. This is happening because the networking script is being run twice. But it also says that lo only is being configured a second time, not eth0. -- Pete -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
