On Mon, 2008-04-21 at 02:26 +0200, Dennis Jacobfeuerborn wrote:
Dan Williams wrote:
- Device: eth0 ----------------------------------------------------------------
Type: Wired
Driver: forcedeth
State: connected
HW Address: 00:00:00:00:00:00
I've seen this once and not been able to reproduce; there might be a
race between bringing up the card and getting a valid MAC address since
sometimes the MAC can't be read until firmware is loaded and booted, but
that's usually only an issue with wireless cards since wired devices
don't usually have firmware.
I actually managed to fix my problem by disabling the "network" service. I
guess the remaining question is why the interface ends up in a b0rked state
when it is first brought up by "network" and then taken over by NM. Should
"network" actually bring the interface up if the config file says
"NM_CONTROLLED=yes"?
No, it probably should not do anything if NM is running.
I think it would be useful to define the semantics when both services are
started. Should there be two sets of interfaces determined by NM_CONTROLLED
and each service only caring for its "own" so that they don't collide or
should this work like an override mechanism where one service takes over
interfaces from the service that ran before?
If NM_CONTROLLED=yes and NM is running, only NM should manage the
device. If NM is not running or if NM_CONTROLLED=no, then it's probably
fine for the network service to touch the device.