From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Galeon/1.3.12 Description of problem: The machine is a Dell C400 laptop with builtin PCMCIA wireless. The network was configured through system-config-network to never bring up any of the network connections during boot (since the laptop moves between several network environments). However on boot, this setting seems to be ignored by the PCMCIA startup scripts and the wireless interface is initialized and made active. There is a bit of code in /etc/pcmcis/network.opt which seems suspect: if [ -z "$IPADDR" -a -f /etc/sysconfig/network-scripts/ifcfg-$2 ] ; then INFO="Red Hat netconf setup" start_fn () { . /etc/sysconfig/network-scripts/ifcfg-$1 if [ "$ONBOOT" = "yes" ] ; then log /sbin/ifup $1 ; fi } stop_fn () { log /sbin/ifdown $1 } fi but my bash scripting is not up to par, so this could be okay. I was just wondering about the switching between $1 and $2. Version-Release number of selected component (if applicable): initscripts-7.48-1 How reproducible: Always Steps to Reproduce: 1. boot system 2. ifconfig 3. Actual Results: /dev/eth2 (wireless card) is active. Expected Results: no external interfaces should be active Additional info:
You can add 'ONHOTPLUG=no' to the config file; that should solve this.
It's actually 'HOTPLUG=no'. 'ONBOOT=NO' also works. But since these config files will be overwritten by the system-config tools, and HOTPLUG=no is not an option in the config files, is this not still a bug in the network configuration tools?
Well, *ideally* this will all get replaced by 'onlink=<yes|no>', and that will apply to boot, hotplug, or whatever. Or something similar. But that's not been coded up yet.