Bug 99294 - nameif doesn't allow one to assign names with MAC address
Summary: nameif doesn't allow one to assign names with MAC address
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: net-tools (Show other bugs)
(Show other bugs)
Version: 9
Hardware: i386 Linux
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-17 04:36 UTC by Yusuf Goolamabbas
Modified: 2015-03-05 01:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-19 12:30:21 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Yusuf Goolamabbas 2003-07-17 04:36:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030706
Mozilla Firebird/0.6

Description of problem:
Hi, I am trying to hardwire my ethernet interfaces names with the use of nameif,
however when I create the appropiate /etc/mactab file for a machine containing 3
Intel EEpro cards
I get the following message

Cannot change name of eth2 to eth0: File Exists

I suspect it may be due to naming conflicts, I think this is better
described here


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create /etc/mactab
2. Introduce nameif in the networking script
   I used the technique described in Randy Dunlap's mini-howto


Randy's changes were done on a Mandrake 9.0 installation

Actual Results:  Interface names not wired according to mac address

Additional info:

Possible bug fix described here


Comment 1 Phil Knirsch 2003-08-19 12:30:21 UTC
Fixed in latest initscripts. Now you can use any kind of interface name (e.h.

That should help.

Read ya, Phil

Comment 2 Yusuf Goolamabbas 2003-08-25 07:48:55 UTC
Phil, Any chance that is going to be queued for an errata release

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