On Tue, Apr 19, 2011 at 03:37:50PM +0200, Marco d'Itri wrote: > On Apr 19, rleigh <rle...@codelibre.net> wrote: > > > (eth0 is configured here after changing the config to force it to use > > dhcp). Since the interface is already "up", maybe that's the reason > > the events aren't generated. So I guess the question now is, what's > > bringing up the interface before ifupdown does? Could it be udev? Or > > something else in early boot or the initramfs? > Definitely not udev. uevents for wired interfaces are generated when > they appear and disappear, they do not follow link state. > If eth1 is up but is not mentioned in interfaces then I have really no > ideas, but if they are both configured in interfaces to use dhcp and > after the boot they are up but dhcp did not work then the problem is > dhcpd failing. > I highly recommend that you boot the system with init=/bin/bash and > manually run each rcS.d init script to see exactly what is happening.
Finally pinned down the cause on my system. If the dnet-common package is installed, this triggers installation of the decnet kernel module at boot. Not sure whether the init script or the kernel module cause the problem, but when they are installed, DHCP doesn't work, and when removed, I get working DHCP at reboot. It looks like dnet-common can mess with the NIC's MAC address, which might be a potential issue. Whatever the reason, it's not an issue with udev or ifupdown. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
