Ubuntu
udev package

network interfaces not properly configured

Bug #149319 reported by Ruben Laban
8
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After a clean install of Ubuntu Gutsy Gibbon on a Dell PowerEdge860, the network configuration is more or less messed up.
During installation there's an eth0 and eth1 interface (two broadcom nics, tg3 driver), which are configured fine. Yet after first reboot the devices appear as eth2 and eth3, due to another (busybox) bug.
However destroying the contents of /etc/udev/rules.d/70-persistent-net.rules, nor deleting the actual file, only fixed the problem partially for me. After rebooting the devices do show up as eth0 and eth1, however the file /etc/udev/rules.d/70-persistent-net.rules remains empty (when having destroyed the contents before rebooting) or non-existent (when having deleted the file).
What I'm trying to accomplish is to rename my interfaces to custom names like int0/ext0/wan0/etc.

Revision history for this message
Ruben Laban (r-laban) wrote :

After some troubleshooting with help from soren and ivoks on IRC, we found out that a restart of udev (sudo /etc/init.d/udev stop && sudo /etc/init.d/udev start) in fact does populate the file /etc/udev/rules.d/70-persistent-net.rules properly.

Also in order to have the file properly generated when the interface names were already renamed, it required a modification of /etc/udev/rules.d/75-persistent-net-generator.rules to include wildcards that'd match the renamed interfaces.

Revision history for this message
Ruben Laban (r-laban) wrote :

Some more information that might be related to this issue: /var/log resides on a separate partition (lvm volume on software raid) which causes some errors during boot. It complains about a command similar to 'mv /dev/.udev.log /var/log/udev.log'. This fails because /var/log isn't available at that point yet.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Yup, exactly right -- this fails and then subsequently the rest of the script isn't run (which copies the networking rules in)

this init script should be later in the boot sequence than it is

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

udev (113-0ubuntu16) gutsy; urgency=low

  * Rename the finish init.d script to udev-finish, and move from S23 to
    S37 so it runs after /var has actually been mounted. This would
    otherwise cause a missing udev.log and non-generation of the persistent
    rules. LP: #149319.

 -- Scott James Remnant <email address hidden> Fri, 05 Oct 2007 16:21:58 +0100

Changed in udev:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.