Bug 1029815 - net.ifnames=0 don't work
net.ifnames=0 don't work
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-11-13 04:47 EST by Terje Røsten
Modified: 2013-11-13 07:11 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-13 07:11:03 EST
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 Terje Røsten 2013-11-13 04:47:39 EST
Description of problem:

Even with net.ifnames=0 passed as kernel cmdline, systemd-udev insist on renaming
net interfaces. 

Please stop. 

Comment 1 Michal Schmidt 2013-11-13 05:22:49 EST
net.ifnames=0 is not meant to disable the entire udev's interface renaming ability. It merely disables the udev rule that assigns interfaces the names according to the scheme described in http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

There are a few other ways your interfaces may get their names assigned:
 - by biosdevname
 - by /etc/sysconfig/network-scripts/ifcfg-* config files
 - by custom rules in /etc/udev/rules.d/

What are the exact names that you're getting?
Comment 2 Terje Røsten 2013-11-13 05:57:46 EST
Removing biosdevname package fixed the issue. 

However, this seems messy, why the need for both systemd-udev renaming and biosdevname?

I keep disabling more and more stuff in each Fedora release...

Close ticket if you want.

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