Bug 824165 - Persistent network devices not work
Persistent network devices not work
Product: Fedora
Classification: Fedora
Component: udev (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: udev-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-05-22 16:56 EDT by Milan Kerslager
Modified: 2013-08-01 08:56 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 08:56:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milan Kerslager 2012-05-22 16:56:04 EDT
I have current F17 RC (by "yum update"). The file /etc/udev/rules.d/70-persistent-net.rules has not been created when the system was installed. I have two NICs. Every reboot random order is picked even I have "HWADDR=..." in both ifcfg-eth0 and ifcfg-eth1. So my firewall does not work. I have to reboot to get correct order, but next reboot the order is reversed...
Comment 1 Nathan Miller 2012-06-01 03:28:48 EDT
I'm seeing the same thing on a F17 clean minimal install.  Upon further research I found that /lib/udev/write_net_rules does not exist either.  It was my understanding that /etc/udev/rules.d/70-persistent-net.rules is created by that.  

I've also been reading that this was going away in the future but I couldn't find any clear documentation stating such.  If so, that is fine, but is there any further documentation on this?  I'd rather not use biosdevname and be able to control the naming of my interfaces myself.  

When I remove biosdevname and NetworkManager all 5 of my interfaces show up and are named eth0 through eth4, but I'm curious how and where I can change the names to fit my needs now that udev is no longer generating rules?
Comment 2 Petr Tuma 2012-06-02 15:16:12 EDT
Milan: Installing package biosdevname should give you /lib/udev/rules.d/71-biosdevname.rules, which should rename all eth* devices to names derived from their location (for example slot in PCI). This should probably help you.

No idea why the rule to write out persistent device names was dropped (there seems to be a leftover rule from initscripts, which exports INTERFACE_NAME from network configuration scripts, but that is probably no longer used).
Comment 3 Fedora End Of Life 2013-07-04 00:11:13 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2013-08-01 08:56:26 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.