Bug 539669 - wireless initscripts wants iw tool, but not depends on it
Summary: wireless initscripts wants iw tool, but not depends on it
Status: RESOLVED FIXED
: 544665 (view as bug list)
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Factory
Hardware: x86-64 SUSE Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-16 16:51 UTC by Tomas Konir
Modified: 2021-02-26 20:24 UTC (History)
5 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Konir 2009-09-16 16:51:07 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-3.5 Firefox/3.5.2

script /etc/sysconfig/network/scripts/ifup-wireless tests if iw command exists (test is at line 185) and refuse to enable wireless interface if iw not found. Sysconfig package (where mentioned script belongs to) don't depend on iw package. This cause not working wireless interface after upgrade.

Reproducible: Always

Steps to Reproduce:
1. upgrade from milestone6 to current factory
2. reboot
3. try rcnetwork restart


Actual Results:  
Setting up network 
interfaces:    eth0      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)                                                                                          
    eth0      IP address: 192.168.172.1/24                                                                                                                                                                    
    eth0                                                                                                                                                                                                  done
    wlan0     name: ASUSTeK BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller                                                                                                                        
cannot find 'iw', please install                                                                                                                                                                              
    wlan0                                                                                                                                                                                                 done
Setting up service network  .  .  .  .  .  .  .  .  .  . 

Expected Results:  
Setting up network interfaces:                                                                                                                                                                                
    eth0      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)                                                                                          
    eth0      IP address: 192.168.172.1/24                                                                                                                                                                    
    eth0                                                                                                                                                                                                  done
    wlan0     name: ASUSTeK BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
    wlan0     starting wpa_supplicant
    wlan0     Starting DHCP4 client. .
    wlan0     IP address: 172.16.42.42/24 (moje)
    wlan0
Comment 1 Marius Tomaschewski 2009-09-21 09:08:42 UTC 
Yes,
there is a new requirement because of wireless regulatory domain.

Sysconfig provides only rpm dependencies to configure 'normal eth'
interfaces -- all another are considered optional and requested by
yast2 network when such interface is in use.
Comment 2 Marius Tomaschewski 2009-09-21 09:13:23 UTC 
Michal,

can you add the new wireless dependency/check for 'iw' utility/package
to the next yast2 network? Thanks!

[BTW: Another way would be to split sysconfig into several packages
 and maintain the dependencies there. But this is nothing for 11.2.]
Comment 3 Marius Tomaschewski 2009-10-02 11:12:10 UTC 
*** Bug 541717 has been marked as a duplicate of this bug. ***
Comment 4 Marius Tomaschewski 2009-10-02 11:19:36 UTC 
Ahm...
yast2 is not doing anything while update and can not fix it...

I'll change the check to complain only when the 'iw' utility
is really required.
Comment 5 Marius Tomaschewski 2009-10-02 11:34:55 UTC 
In OBS, Base:System/sysconfig, submit request to factory 21578.
Comment 6 Marius Tomaschewski 2009-10-02 11:39:15 UTC 
ahm... a typo. new request id 21579
Comment 7 Marius Tomaschewski 2009-10-07 16:48:39 UTC 
*** Bug 544665 has been marked as a duplicate of this bug. ***
Comment 8 Michal Zugec 2009-10-20 09:52:43 UTC 
fixed in yast2-network-2.18.51
Comment 9 Bernhard Wiedemann 2016-04-15 09:52:54 UTC 
This is an autogenerated message for OBS integration:
This bug (539669) was mentioned in
https://build.opensuse.org/request/show/21579 Factory / sysconfig