Red Hat Bugzilla – Bug 478349
Problem with NetworkManager managing two wireless adapters and wireless kill switch
Last modified: 2009-02-12 19:23:50 EST
Description of problem:
The configuration is this: HP nx7000 notebook with integrated Intel 2100 adapter (802.11b) and external USB wireles adapter Linksys WUSB300N (802.11b,g,n). Both devices handled by NetworkManager. However there is a catch: The hardware wireless kill switch set off tells the NetworkManager that both adapters are disabled. This is not true. The USB can be brought to life by
executing the following commands under root
# service NetworkManager stop
# service wpa_supplicant restart
# dhclient -v wlan0
When the NetworkManager service is running and the wireless kill switch make the wireless active, both interfaces do connect to the same network and get different IPs. I know this can be corrected by configuration (setting MAC address of the device) but it will make things a little bit complicated at user side as sometimes I connect via i2100, sometimes with WUSB300N (when available).
And anyway, to connect via WUSB300N I do not need integrated i2100 active to drain power from the notebook.
As a naive user I would expect that hardware wireless kill switch on the notebook only operates on the integrated wifi card, not the external one. In fact the external one is not affected at all, just the NetworkManager thinks so. And that is the problem I ask to fix.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. connect external USB wifi card (Linksys WUSB300N), firmware installed, ndiswraper installed, configured
2. boot the computer with wireless kill switch off
No connection is made.
Network manager menu says:
Wireless Network (Intel Samsung X10/P30 integrated WLAN)
wireless is disabled
Wireless Network (Linksys Wireless-N USB Network Adapter v1021)
wireless is disabled
Connection to a wireless network is made via WUSB300N
Few weeks ago in Fedora 9, it has worked (i.e. WUSB300N got connected) for a short time. But around the time of the infamous d-bus downgrade it got broken again.
Current policy is that the rfkill switch applies to *all* devices of that class. Furthermore, there aren't good kernel-level mechanisms to distinguish which rfkill switches apply to which devices at this time, because there are no strong ties between the switch and the specific wifi device. It's a combination of technical issues that can't be easily solved, and policy decisions to make things less complicated for everyone. Unfortunately, this won't be fixed for a while.