Bug 729815

Summary:	udev renaming eth0 to p33p1
Product:	[Fedora] Fedora	Reporter:	Paul Bransford <draeath>
Component:	biosdevname	Assignee:	Praveen K Paladugu <praveen_paladugu>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	15	CC:	harald, jonathan, kay, matt_domsch, mebrown, narendra_k, pbrobinson, praveen_paladugu
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-17 09:36:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Bransford 2011-08-10 22:21:58 UTC

I'm not sure if this is udev or the kernel at fault, or someone else entirely.

Kernel module atl1e is loading my ethernet device (only other network device is wireless) as eth0, and udev renames it to 'p331'. Device ID is: 1969:1026 (rev b0)

This upsets several programs that expect certain names, and is totally unexpected operation.

I unfortunately do not know how to drill down and discover exactly why udev is doing what it is doing.

Comment 1 Harald Hoyer 2011-08-11 07:43:57 UTC

can be turned off by adding "biosdevname=0" to the kernel command line

Comment 2 Peter Robinson 2011-10-17 09:36:11 UTC

(In reply to comment #0)
> I'm not sure if this is udev or the kernel at fault, or someone else entirely.

neither. Its this feature: https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming

> Kernel module atl1e is loading my ethernet device (only other network device is
> wireless) as eth0, and udev renames it to 'p331'. Device ID is: 1969:1026 (rev
> b0)

It does the same on my netbook with this device but I've only seen issues with ekiga (long fixed).

> This upsets several programs that expect certain names, and is totally
> unexpected operation.

Well it should actually make no difference as the network device name should make no difference. Its a bug in the application, not the name of the network interface.

> I unfortunately do not know how to drill down and discover exactly why udev is
> doing what it is doing.

You can probably just remove the biosdevname package, but not sure if this is supported.