Network Initialization at boot takes a long time

[alan at comm-tech.org]

You will probably find your /etc/network/interfaces has something like
this in it:

auto eth1
iface eth1 inet dhcp

The line "auto eth1" will cause Ubuntu to try to get an ip address for
eth1 at bootup. If there is no dhcp server available at that time, this
will fail and bootup will appear to hang at this time. (DHCP server can
be temporarily inaccessible for many reasons, for instance my network
uses wep and the wep key is not specified in interfaces)

Best solution I got is just to comment out the "auto eth1" line, and
issue a "sudo ifup eth1" after bootup when you actually need the
interface.

========================

On Sun, 2005-02-20 at 23:42, Michael Scottaline wrote:
> On Sun, 20 Feb 2005 22:15:23 +0000, David Unger <dsunger6 at hotmail.com> wrote:
> > I'm running Warty on an Inspiron 600m, with an Intel(R) PRO/Wireless
> > 2200/2915 card and a Tigon3 (I think) ethernet card.  Both work fine, but
> > during the boot process, the kernel spends a very long time on the 'Network
> > Initialization' stage.  How can I find out what its doing for so long?
> =======================
> Have you tried to run dmesg???????
> Mike
> 
> -- 
> "I don't know how World War III will be fought, but I do know World 
> War IV will be fought with sticks and stones" 
> - Albert Einstein