Bug 30363 - network center chooses first bssid rather than strongest
Summary: network center chooses first bssid rather than strongest
Status: RESOLVED DUPLICATE of bug 23453
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-02 20:01 CEST by w unruh
Modified: 2022-05-10 21:26 CEST (History)
1 user (show)

See Also:
Source RPM: networkcenter, wpa_supplicant
CVE:
Status comment:


Attachments

Description w unruh 2022-05-02 20:01:31 CEST
Description of problem:
If there are a number of BSSID associated with the same SSID name, wpa_supplicant chooses the first one it comes across rather than the one with the strongest signal. This often results in an association with a flaky weak signal in Netwrk Center rather than with a solid strong one. One way might be to use the wpa_cli command 
bssid <network id> <BSSID> = set preferred BSSID for an SSID
to force wpa_supplicant with the strongest SSID

Of corse this dos not solve the eternal problem with network center that if there are too many BSSID in a region, "wpa_cli scan_results " reports nothing, with wext driver because wext reports nothing (eg bug 17706 a 6 year old bug)

Version-Release number of selected component (if applicable):


How reproducible:Always


Steps to Reproduce:Connect using Network Center. It will often connect to a weaker signal than strongest.

I guess the person who set up Network Center stopped, and no-one else has stepped in to keep up maintenance .
Comment 1 Marja Van Waes 2022-05-10 21:26:52 CEST
Duplicate.

You're right, sometimes someone fixes something in drakx-net, but those someones are always contributors with too many other things on their to-do lists.

*** This bug has been marked as a duplicate of bug 23453 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
CC: (none) => marja11


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