Bug 17104

Summary: interfaces configured with TYPE=Wireless are not started on boot
Product: Mageia Reporter: Yves DEMUR <yves.demur>
Component: RPM PackagesAssignee: Colin Guthrie <mageia>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: initscripts-9.55-13.mga5.src.rpm CVE:
Status comment:

Description Yves DEMUR 2015-11-07 10:46:24 CET
Description of problem:
In file /etc/rc.d/init.d/network, lines 117-119 and 209-211 there are 2 identical blocks

                if [ "$TYPE" = "Wireless" ]; then
                        continue
                fi

which deselect wireless declared interfaces from starting or stopping list. This is wrong because wireless may be wanted started at boot, and the wish of no boot start is managed by the ONBOOT variable. These 2 blocks must be deleted or disabled (#).

Steps to Reproduce:
1.Configure a Wireless NIC (ex : ra0)
2.Add the line
TYPE=Wireless
in the /etc/sysconfig/network-scripts/ifcfg-ra0 file and check the ONBOOT=yes
3.Launch the 3 commands
ifdown ra0 boot
systemctl restart network.service
ifconfig ra0
Notice ra0 is not started


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-11-11 17:02:05 CET
Assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 2 Colin Guthrie 2015-11-12 10:01:30 CET
I think you misunderstand what TYPE="Wireless" means in an ifcfg file. It actually represents the details of a wireless *network* not a wireless *interface*.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 3 Colin Guthrie 2015-11-12 10:06:22 CET
Just to explain further, some apps (like network manager with the ifcfg-rh plugin) and our own tools may write out ifcfg-$SSID files for wireless network connection details. There may also key-$SSID files in that folder. I'd argue that this is a silly system and the naming conventions suck, but it is what it is.