Description of problem: When wpa_supplicant is running, draknetcenter doesn't show any wireless network in cauldron, while lots of wireless network are available (intel 5100, driver iwlwifi). I found that wpa_cli -i wlan0 scan_results now reports signal strength with negative value (in dBm). In mga2, on the same system, the signal strength was reported with positive value. I don't know if this change came from new kernel, or new wpa_supplicant. eg. wpa_cli -i wlan0 scan_results Selected interface 'wlan0' bssid / frequency / signal level / flags / ssid ab:cd:ef:ab:cd:e1 2412 -49 [WPA-PSK-TKIP+CCMP][WPS][ESS] wifi-1 ab:cd:ef:ab:cd:e2 2437 -58 [WPA-PSK-TKIP+CCMP][WPS][ESS] wifi-2 ab:cd:ef:ab:cd:e3 2427 -67 [WPA-EAP-TKIP][ESS] wifi-3 ab:cd:ef:ab:cd:e4 2462 -68 [WPA-PSK-TKIP+CCMP][ESS] wifi-4 ab:cd:ef:ab:cd:e5 2462 -61 [WPA2-EAP-CCMP][ESS] wifi-5 ... drakx-net doesn't handle these negative values for signal strength, so that draknetcenter doesn't show any wireless network. First step, in monitor.pm/list_wireless at line 35 $results =~ /^((?:[0-9a-f]{2}:){5}[0-9a-f]{2})\t(\d+)\t(\d+)\t(.*?)\t(.*)$/mg doesn't match negative values for signal strength. I tried to modify this line to match negative values of signal strength, but it's not sufficient. The signal strength reported in dBm (negative values) should probably need to be convert in % (positive values). (just for the test, if I simply reverse the sign (signal_strength = -signal_strength), draknetcenter shows the wireless networks, but of course they are not sorted correctly !!). Version-Release number of selected component (if applicable): drakx-net-1.16-1, wpa_supplicant-1.0-4, kernel-desktop-3.6.5 How reproducible: always
I am seeing the same thing using mga3beta1 upgraded to current Cauldron Hardware is Asus eee 701 from lspcidrake ath5k : Atheros Communications Inc.|AR242x / AR542x Wireless Network Adapter (PCI-Express) [NETWORK_ETHERNET] (rev: 01) # wpa_cli -i wlan0 scan_results bssid / frequency / signal level / flags / ssid 00:26:44:62:4f:11 2462 -30 [WEP][ESS] ST780wl 06:18:84:40:51:3d 2417 -78 [WPA-PSK-TKIP][ESS] MyPlace 7c:03:4c:90:45:23 2437 -91 [WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP][WPS][ESS] SKY04522 00:fe:f4:0b:83:28 2437 -92 [WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP][ESS] BTHub3-9TQP draknetcenter does not show any wireless networks at all, although the wireless connection is up and working. Pressing the 'Refresh' button does nothing.
CC: (none) => derekjenn
Do review my reported bug: https://bugs.mageia.org/show_bug.cgi?id=8580 is this what is happening to you?
CC: (none) => wilcal.int
Whiteboard: (none) => 3Beta1
Created attachment 3333 [details] In and out of WiFi range testing
Created attachment 3361 [details] Patch to allow wpa_cli to report signale strength in dBm I found the code in libDrakX/network/monitor.pm that performed the scan of wireless networks and produced this patch. The patch allows signal strength to be reported either as a positive or negative number If signal strength is negative it will convert signal strength to a percentage based on an arbitary scale (which I am sure could be improved upon) It works for me with mga 3b1 using the ath5k driver. WDYT?
Keywords: (none) => PATCH
Testing has confirmed this bug exists whenever monitor.pm uses either mandi or wpa_cli to discover wireless networks (when roaming is enabled) Signal strength is now reported by mandi and wpa_cli as a negative number in dBm It is not known if this is true for all wireless drivers. When iwpriv is used to discover wireless networks draknetcenter behaves normally. Raising Priority based on discussion in weekly QA meeting. Affected users are unable to select a wireless network other than when the connection is initially defined.
Priority: Normal => HighStatus: NEW => ASSIGNED
assigned is when the assigned person is willing to fix, which is not the case for yet here
Status: ASSIGNED => NEW
*** Bug 8580 has been marked as a duplicate of this bug. ***
Patched monitor.pm on mga3beta2. Confirmed working for ath9k driver, at least it shows my own network while 'iwlist scan' shows 4 more networks. Will test i586 with Broadcom BCM4312...
CC: (none) => molch.b
Priority: High => release_blockerCC: (none) => thierry.vignaudWhiteboard: 3Beta1 => 3Beta2
Tested on MGA3Beta2 with i586 Broadcom BCM4312 - works.
This could affect alot of people, is it worth a beta2 rebuild to include the patch? See also bug 8804
CC: (none) => eeeemail, ennael1, tmb
*** Bug 8804 has been marked as a duplicate of this bug. ***
Fixed in drakx-net-1.18-1.mga3 Thanks for the patch.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Summary: drakx-net doesn't handle signal strength reported in dBm (negative values) => [RESOLVED]drakx-net doesn't handle signal strength reported in dBm (negative values)