Hide Forgot
Description of problem: I have several profiles created with redhat-config-network. If the interfaces use dhcp and a non-default nickname, I get errors from /sbin/dhclient It looks like what happens is that the scripts in /etc/sysconfig/network-scripts get created based on the nickname of the interface, eg. ifcfg-eth0_dhcp. When the interface is activated, the name eth0 is passed to /sbin/dhclient-script, which generates errors, because it is expecting to find a file named /etc/sysconfig/network-scripts/ifcfg-eth0, rather than the file which is actually there: /etc/sysconfig/network-scripts/ifcfg-eth0_dhcp Version-Release number of selected component (if applicable): How reproducible: Very Steps to Reproduce: 1. Create a new profile 2. Create an interface in the that profile with a nickname, e.g eth0_dhcp. It should get the IP address using dhcp 3. Activate that interface Actual results: Error from /sbin/dchclient-script: configuration for eth0 not found Expected results: eth0 should be activated without errors Additional info: If the nickname is changed back to eth0, things work properly
I tried to overcome this problem by creating several nicknames to the same device (eth0_dhcp as eth0, eth0_home as eth0:1 - using alias 1) and make them active in different profiles - but unfortunately aliases (eth0:1 etc) are not activated during the boot process. Should I fill special bug about this - or can we discuss this here as well?
Experiencing the same problems. This makes profiles useless which in turn makes networking on laptops a pain. I'd love to try to offer a fix, but I'm not sure what the intended behavior is, whether it should be ifup <nickname> or ifup <deviceid>.
Under RH9, the script that is created in /etc/sysconfig/network-scripts is "ifcfg-eth0" and is activated by saying "ifup eth0" even if eth0 has a different nickname.
yes, i know that to be true, but looking at the current state it's unclear whether the current behavior is a bug or a half completed move to a new scheme. =(
this is a new naming scheme and should be fixed in dhclient or the initscript that calls dhclient should provide the config file name. reassigning to initscripts
Please attach the config files in use.
I'm not sure what you mean by the config file? Do you mean /etc/sysconfig/network-scripts/ifcfg-eth0_dhcp
Whatever ifcfg file is causing the error, and your /etc/modules.conf.
from what i remember, it's not a problem with the scripts. It's the fact that initscript is calling 'ifup eth1' but redhat-config-network names the scripts 'ifcfg-eth1-<alias>' so the script ifcfg-eth1 doesn't exist and dhclient-script or whatever it is bombs out with a file not found error
Hey, I can't reproduce the problem now! I do pull updates for this system, and I see that there has been an update to initiscripts since I wrote this bug report. Maybe it got fixed.
There were some fixes in initscripts in the update - please reopen if it persists.