Mailinglist Archive: opensuse-factory (818 mails)
| < Previous | Next > |
[opensuse-factory] eth0 set to activate at boot time by default? - dhcp runs even when eth0 unplugged
- From: Willem Meens <opensuse-ml@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Oct 2008 22:09:24 +0100
- Message-id: <1225314564.6672.8.camel@OSU111b>
Hi All,
Was wondering if others have noticed this too:
When booting and also when restarting the network service, openSUSE is
trying to get an address for an unplugged Ethernet port - resulting in
an unnecessary delay.
Turns out the network device defaults to 'activate at boot time' instead
of 'on cable connect'. I've noticed this with a clean install of beta2
and beta3.
Might be relevant: this is on a Dell Latitude laptop that has a Broadcom
(b44) nic.
Anyone else having this?
note: I've also installed the Xen packages.. could be this sets the nic
to always be active? Will check this is related on my next fresh beta4
install.
Thanks,
Wj
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Was wondering if others have noticed this too:
When booting and also when restarting the network service, openSUSE is
trying to get an address for an unplugged Ethernet port - resulting in
an unnecessary delay.
Turns out the network device defaults to 'activate at boot time' instead
of 'on cable connect'. I've noticed this with a clean install of beta2
and beta3.
Might be relevant: this is on a Dell Latitude laptop that has a Broadcom
(b44) nic.
Anyone else having this?
note: I've also installed the Xen packages.. could be this sets the nic
to always be active? Will check this is related on my next fresh beta4
install.
Thanks,
Wj
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |