Bug 123034
| Summary: | Using nicknames causes problems with dhclient-script | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
| Component: | dhcp | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | pierre-bugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 19:03: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: | |||
This bug is reproducable on Core 2 as well. The problem is that dhclient will execute dhclient-script which will execute a method (need_config) from the script /etc/sysconfig/network-scripts/network-functions. The problem is, dhclient works with the real interface name (eg ethx, etc...) while if you use nicknames, the config files will be renamed ifcfg-<nickname>. Thus, when the method need_config is passed the real name of the interface to setup, it will try to find the config file ifcfg-ethx and won't find it... *** This bug has been marked as a duplicate of 124022 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 Description of problem: I've created two wireless device configurations that use the same hardware device ("eth2"), one with a specified SSID and key, and one without. I want to call one "CoRAwlan" and the other "wlan" using nicknames. However, once I've done that, when I activate the network I get the following output: Determining IP information for eth2.../sbin/dhclient-script: configuration for eth2 not found. /sbin/dhclient-script: configuration for eth2 not found. /sbin/dhclient-script: configuration for eth2 not found. /sbin/dhclient-script: configuration for eth2 not found. and this repeats forever, though the interface does come up okay. Another note - when adding a second "interface" to a wireless device, I don't think it should set the device alias to "1" (or anything). Version-Release number of selected component (if applicable): redhat-config-network-1.3.10-1 How reproducible: Always Steps to Reproduce: 1. see above 2. 3. Additional info: