eth0 not mapped by hotplug
Bug #19641 reported by
Martin Meredith
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hotplug (Ubuntu) |
Fix Released
|
Critical
|
Scott James Remnant (Canonical) |
Bug Description
This morning, I did a dist-upgrade on breezy to find that my network was no
longer being auto-started, which was very confusing for a while.
I checked out /etc/network/
mapping eth0
mapping hotplug
script grep
map eth0
However, this was not the case, and I had to add eth0 to the "auto" section of
the interfaces file.
This was very confusing, and I thought something was broken with the kernel...
Also, on boot, i recieve the following error when hotplug starts:
Warning: Interface is eth0 at line 2, cannot be mapped reliably.
To post a comment you must log in.
I see this too, although unfortunately I don't have time to fix it. The problem
seems to be that (a) the module now appears in the initramfs, so eth0 is brought
up then, but the initramfs doesn't have hotplug (fair enough); (b) it used to be
possible to coldplug network interfaces later on, but there's no longer an
/etc/hotplug/net.rc so this doesn't happen, and the net event for eth0 is never
received outside the initramfs. Normally net.ifup would run when the hotplug
event is first received and then wait until the hotplug-net init script is run,
but this doesn't work in an initramfs situation.
There's discussion of this in Debian bugs #296640 and #303671, at least. Jeff,
could you please look at this fairly urgently? It breaks network-enabled
installations, because base-config expects to be able to download language packs
from the network and then suddenly finds that it can't.