interfaces not renamed (iftab) after resume

Bug #64381 reported by FuturePast
10
Affects Status Importance Assigned to Milestone
udev
Fix Released
Undecided
Scott James Remnant (Canonical)
acpi-support (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I specify network interfaces to be renamed in /etc/iftab.

On resume after suspend-to-ram, my network interfaces are given the typical eth0 etc. names, which is useless as my settings depend on the names as specified in iftab.

Using daily-updated edgy on Dell Latitude D600.

Revision history for this message
FuturePast (4uturepast) wrote :

Running /etc/init.d/udev restart after resume fixes problem.

Revision history for this message
Pedro Martinez-Julia (pedromj) wrote :

It happends and it's very important because in many systems the name of the interface could change after suspend (or change in any boot).

Changed in acpi-support:
status: Unconfirmed → Confirmed
Changed in udev:
status: Unconfirmed → Confirmed
Revision history for this message
Paul Sladen (sladen) wrote :

Scott: this sounds like your kind of area; who do you think should be responsible. My hunch it would be the kernel?

Changed in udev:
assignee: nobody → keybuk
Revision history for this message
Paul Sladen (sladen) wrote :

Is this issue still around with the latest Feisty beta?

Revision history for this message
Michael Robinson (michael-livia) wrote :

No, it's not in the latest Feisty beta (having upgraded).

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

Other bug subscribers

Remote bug watches

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