On 20/05/12 20:03, James Harper wrote:
I am running Debian testing and after a recent dist-upgrade networking no longer comes up automatically after booting. eth0 doesn't come up and more surprisingly neither does the loopback interface.
I can configure these manually after booting but would obviously like to have the interfaces come up during boot process.
During the upgrade a new networking program 'dnet' appears to have been installed which I suspect is related to this problem. During the install it wanted to be configured so it could change the mac address of my nic. Until it was configured eth0 was dead and wouldn't come up at all.
Does anyone know what's wrong and how I can fix it? I'm tempted to uninstall dnet but it's obviously been installed for a reason. I've googled around and haven't been able to find anything that helps with a fix.
Any messages in the logs about firmware? That wouldn't explain the loopback interface though.
I don't know what dnet is (unless you are running DECnet :)... whatever it is, maybe you could do dpkg-reconfigure on it to get it to ask you the configuration questions again in case you made a typo?
dnet-common is a DECnet package, do you know why that would have been dragged in on my last dist-upgrade. I did a dependency check and the only package that it depends on libroar2. DECnet doesn't look particularly useful? Anyways I checked /var/log/dpkg.log to see exactly what the last dist-upgrade did and found that ifupdown had been removed!! Re-installed that and networking starts on boot again. Cheers Geoff
James
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main