Bug 25478 - Network Manager reports wrong access point is connected.
Summary: Network Manager reports wrong access point is connected.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Jani Välimaa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-27 17:57 CEST by w unruh
Modified: 2020-08-23 15:46 CEST (History)
1 user (show)

See Also:
Source RPM: netoword Manager
CVE:
Status comment:


Attachments

Description w unruh 2019-09-27 17:57:03 CEST
Description of problem: Network Manager reports the wrong access point is connected. 


Version-Release number of selected component (if applicable):libdrakx-net-2.32.2-1.mga6


How reproducible:
Often

Steps to Reproduce:
open  wireless in the Network Manager window in a place where there are
many access points with the same name (in my case eduroam, where there are about 10 ESSIDs for the same name eduroam)
3.click on the first (strongest signal) to connect.
After connection the blue bar is supposed to indicate which AP is connected to.
However, the blue bar is on one of the lowest ones (weak connection), while, if I look at the wpa_supplicant logs, it connected to the strongest one. 
Ie, NetworkManager seems to somewhat randomly pick a Ap to display as the connected AP

It would also help in troubleshooting if the gui window also reported the ESSID of the various APs so one could distinguish the various ones with the same name.
Comment 1 Lewis Smith 2019-09-28 10:34:00 CEST
Assigning to wally as NetworkManager maintainer.

Assignee: bugsquad => jani.valimaa

Comment 2 Aurelien Oudelet 2020-08-23 15:46:41 CEST
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

CC: (none) => ouaurelien
Resolution: (none) => OLD
Status: NEW => RESOLVED


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