Bug 119847 - builtin wireless does not honor ONBOOT=no
builtin wireless does not honor ONBOOT=no
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2004-04-02 11:40 EST by Bill Rankin
Modified: 2014-03-16 22:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-02 12:28:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Rankin 2004-04-02 11:40:28 EST
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

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):

How reproducible:

Steps to Reproduce:
1. boot system
2. ifconfig

Actual Results:  /dev/eth2 (wireless card) is active.

Expected Results:  no external interfaces should be active

Additional info:
Comment 1 Bill Nottingham 2004-04-02 12:28:56 EST
You can add 'ONHOTPLUG=no' to the config file; that should solve this.
Comment 2 Bill Rankin 2004-04-02 14:00:55 EST
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?
Comment 3 Bill Nottingham 2004-04-02 14:52:04 EST
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.

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