Comment 24 for bug 184711

Revision history for this message
Filofel (filofel) wrote :

I see the same here.

I would add that system > administration > network works.
The only thing that doesn't work (at least here) is gnome-nettool, either command line or as in
system > administration > network tools > {Select interface} > {Configure button>}
It then yelds the infamous "The interface does not exist".

As a side note, I think there is something strange in the interface handling logic when one changes the NIC, anyway. This might or might not be related to the bug we're talking about, but the contents of /etc/network/interfaces
after a NIC change doesn't seem to be what it should be, and it takes a few reboots (with the machine coming up with no interface at all) and manual fixing of the /etc/network/interfaces fix before things get back to normal, and stable. When the machine comes up with no interface at all, I see that something has removed all but the loopback device from /etc/network/interfaces.
I'm trying to understand what goes on there.
Might also be related to what udev does: I've noticed that if I manually load my enet driver at early boot (i.e. while still in initramfs), it appears as eth0. While when the machine is done booting, i.e. after the root partition has been mounted, it appears as eth1.
What I'm seeing when performing a NIC replacement might also happen when using two alternative ways to access the network, like a wired connection and a WiFi one used alternatively.