Bug 197902 - Problem with nicknames different from ethN on dhcp activated network interfaces
Summary: Problem with nicknames different from ethN on dhcp activated network interfaces
Keywords:
Status: CLOSED DUPLICATE of bug 196324
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-07 02:18 UTC by Marcelo Roberto Jimenez
Modified: 2014-03-17 03:00 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-07-28 23:36:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Configuration files for eth0 (230 bytes, text/plain)
2006-07-09 11:14 UTC, Marcelo Roberto Jimenez 		no flags Details
View All

Description Marcelo Roberto Jimenez 2006-07-07 02:18:54 UTC 
Description of problem:
When setting a network interface (e.g., eth0) using system-config-network, if 
the nickname is different from the real device name, bringing up the interface 
fails. In the following, I have set the nickname to eth0Dynamic. Setting it to 
eth0 makes everything work:

# service network start
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0Dynamic:
Determining IP information for eth0.../sbin/dhclient-script: configuration for 
eth0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: eth0: No such file or 
directory
/sbin/dhclient-script: configuration for eth0 not found. Continuing with 
defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: eth0: No such file or 
directory
 done.

# service network stop
Shutting down interface eth0Dynamic:  /sbin/dhclient-script: configuration for 
eth0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: eth0: No such file or 
directory
                                                           [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Disabling IPv4 packet forwarding:  net.ipv4.ip_forward = 0
                                                           [  OK  ]
Comment 1 Bill Nottingham 2006-07-07 02:23:00 UTC 
Can you attach your configs?
Comment 2 Marcelo Roberto Jimenez 2006-07-09 11:14:46 UTC 
Created attachment 132125 [details]
Configuration files for eth0
Comment 3 Marcelo Roberto Jimenez 2006-07-09 11:46:45 UTC 
The problem does not seem to be inside the configuration file, the problem is 
that when you give the interface a nick like eth0Dynamic, the file gets the name 
ifcfg-eth0Dynamic, and dhclient-script is no longer able to find the 
configuration, because it looks for ifcfg-eth0, not ifcfg-eth0Dynamic.
Comment 4 Bill Nottingham 2006-07-10 20:16:54 UTC 
Hm, when was the last time this worked for you?
Comment 5 Marcelo Roberto Jimenez 2006-07-11 13:45:18 UTC 
It works for me, as long as the interface does not use DHCP. A static assignment works fine with a nick e.g. 
eth0Static.
Comment 6 Marcelo Roberto Jimenez 2006-07-11 13:47:07 UTC 
Sorry, that did not answer your question.

It has never worked for me before, but works if the interface does not use DHCP.
Comment 7 Miloslav Trmač 2006-07-28 23:36:28 UTC 
Thank you for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.

*** This bug has been marked as a duplicate of 196324 ***
Note You need to log in before you can comment on or make changes to this bug.