Bug#606279: seems to think everything is a hotpluggable interface
On Tue, Dec 07, 2010 at 07:39:38PM -0400, Joey Hess wrote:
> It's typical for netcfg to put allow-hotplug in /etc/network/interfaces
> for the interface d-i was installed on IME. I get the sense that
> hw-detect.hotplug is buggy somehow:
>
> Dec 3 16:13:37 net/hw-detect.hotplug: Detected hotpluggable network interface lo
> Dec 3 16:13:54 net/hw-detect.hotplug: Detected hotpluggable network interface lo
> Dec 3 16:13:54 net/hw-detect.hotplug: Detected hotpluggable network interface wlan0
> Dec 3 16:14:42 netcfg[4454]: INFO: Detected wlan0 as a hotpluggable device
> Dec 4 01:15:22 net/hw-detect.hotplug: Detected hotpluggable network interface wlan0
> Dec 4 01:15:22 net/hw-detect.hotplug: Detected hotpluggable network interface lo
It's kind of true now - everything gets a udev event on add, and I think
they're all in principle hotpluggable (well, maybe not lo, but it's
handled specially anyway). The relevant meaning of "hotpluggable" is, I
think, that we get a uevent for it appearing.
> This can result in ifup -a not upping it on boot, and a hotplug event
> never bringing it up either.
I wonder why the latter isn't happening? If you're getting a udev event
in d-i, you should get one in the installed system too. That should hit
/lib/udev/rules.d/80-drivers.rules, call /lib/udev/net.agent, and that
should bring up the interface.
It might be worth tracing that chain to find out which bit is breaking.
hw-detect and netcfg seem OK here at least in principle.
--
Colin Watson [cjwatson@debian.org]
Reply to: