wifi UI issues with multiple identical SSIDs

[jstressman]

In our house we have 2 wireless access points, one in the basement and one on the second floor, to provide coverage for the whole house. By default these are both set to the same SSID.

Connecting to the access point down here seems to work fine. I click on the SSID that shows the stronger signal and it goes through and says it's connected. But when I'd click on the network icon in the deskbar, it would show me connected to the wrong one. The one I did NOT click on.

But when I actually opened Network Preferences and click on the Network drop down to list the available access points, it would show me connected to the correct one.

The upstairs one shows the weaker signal, and the downstairs the stronger... in both images. So you can see the two disagreeing on which WAP I'm connected to.

This is the package management nightly r20130920_7cf0e76

[jstressman]

clicking on the network icon shows me connected to the wrong access point. Not the one I actually clicked on.

[jstressman]

opening network preferences and clicking the network drop down shows me connected to the correct SSID.

[korli]

Out of curiosity, you do really have two marvell ethernet devices in your computer?

[jstressman]

Yes.

​https://www.asus.com/Motherboards/P6T_DeluxeOC_Palm/#specifications

Dual Gigabit LAN controllers 2*Marvell88E8056® PCIe Gigabit LAN controller featuring AI NET2

[kallisti5]

while this is in the pm branch, it likely isn't cause by pm. Lets move to the development branch for now.

[axeld]

The Network preferences application shows the wrong one; you are actually connected to the weaker one. So there are two bugs:

• The preferences application shows the wrong one (it only uses the name to determine the associated networks)
• The NetworkStatus application correctly determines the associated network by network address, but connects to a network by name only.

[axeld]

The bug in NetworkStatus is fixed in hrev46108.

[axeld]

The rest was a bit more involved, but should be fixed with hrev46110. Please test; unfortunately, I could not test my changes at all...

[axeld]

Sorry, I messed up the second part (ie. the Network preferences application). I will try to come up with a working solution (that also makes sense) in the next few days/weeks/years.

[waddlesplash]

And we are now using the new network preflet.