Bug 1029815 - net.ifnames=0 don't work
Summary: net.ifnames=0 don't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-13 09:47 UTC by Terje Røsten
Modified: 2013-11-13 12:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-13 12:11:03 UTC
Type: Bug


Attachments (Terms of Use)

Description Terje Røsten 2013-11-13 09:47:39 UTC
Description of problem:

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

Please stop. 


systemd-208-4.fc20

Comment 1 Michal Schmidt 2013-11-13 10:22:49 UTC
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 10:57:46 UTC
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.