afaics it is a problem with dhclient3. Had the same issue in a netboot-scenario. As soon as dhclient (think it was version 3.01) gets called the network interface shuts down. Found this after upgrading an older debian based netboot fs)
Unfortunately the call for dhclient is'nt found in /etc. The documented way to prevent N-M to handle eth0 is to remove the auto-entry from /etc/network/interfaces. Unfortunately all other required initialisation wont be done. The other way is to set eth0 to manual wich works fine for me. Other possibilities are: - use the old-style init scripts - add a (virtual) auto ethX interface to keep N-M running. (loopback is not enough to start network services, nfs ...) - dhclient (necessary if you dont have fix ip addresses and need to refresh the leases...) - fix N-M Imho, there is needed a "already-up" option for interfaces to prevent initialisation in netboot environments. Same for kernel parameters (eg: ip=up) instead of ip=dhcp. This would prevent unneccesary (repeated) dhcp calls. -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
