Search Before Posting
I have searched, but what I found dealt with connecting to a specific network (with one access point). In my case, I would like to force a connection to a specific access point (AP) when there are many access points (APs) in range and all APs are using the same SSID. I thought that I had figured out how to force a connection to a specific AP by creating/saving multiple Network Connections.
Network Connection 1 included the BSSID for AP 1
Network Connection 2 included the BSSID for AP 2
...and so on.
Within each saved Network Connection, the option to "Automatically connect to this network when it is available" was turned off (not selected).
When I wanted to connect to a specific AP, I would...
...edit the Network Connection of interest
...select "Automatically connect to this network when it is available"
...save that Network Connection
...disconnect from the current AP
...reconnect to the applicable SSID
After I was finished with the Network Connection of interest, I would edit/save it again with the option to "Automatically connect to this network when it is available" not selected. At any given time, none (or only one) Network Connection would have the option to "Automatically connect to this network when it is available" selected/saved.
This system worked for a few saved Network Connections, but as I added more - something went haywire. The laptop insisted on connecting to an AP other than the one that I had just set to "Automatically connect to this network when it is available". Disabling/enabling Wi-Fi did not help. Disabling/enabling Networking did not help. Restarting the laptop did not help. The AP that the laptop insisted on connection to was insanely far away - with a Signal level of -89 dBm (per iwconfig). Moving to another part of the building, just caused the laptop to pick another undesired, far away AP to connect to.
When I deleted the Network Connection for the AP that the laptop insisted on using, the laptop simply picked another Network Connection to get stuck on - rendering my "force a connection to a specific AP" scheme useless.
There might be better method/scheme for connecting to a specific AP, but my scheme had an additional benefit: When I don't need to connect to a specif AP, I can save all of the Network Connections with the option to "Automatically connect to this network when it is available" selected. Then (in theory) they laptop would connect to the best AP and I could just look at the "Connection Information" screen to see which AP that I was connected to. The title of the saved Network Connection tells me the AP name - instead of having to look up the BSSID and translate that to a specific AP. But alas, the laptop still insisted on connecting to a uselessly far away AP.
As indicated above, the scheme worked until I added more saved Network Connections. I don't recall the exact number of saved Network Connections where the scheme failed, but the total number of APs that I would like to save a Network Connection for is 10.
The "b43" driver limits my download/upload speeds to roughly 10 to 20 Mbps. An external D-Link USB network adapter that I have reaches closer to 50 Mbps on the same network. Perhaps I did something wrong when installing the "b43" driver. Maybe that is contributing to the laptop getting stuck on connecting to one AP.
 New Questions Deserve New Topics
 Consider Which Forum Section To Post
I hope that this is the correct Forum Section and sub-section.
 Use Informative Titles
How to connect to a specific access point when there are more than one using the same SSID?
...but I opted for brevity.
 Details! Details! Details!
Code: Select all
System: Kernel: 4.13.0-41-generic x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Linux Mint 18.3 Sylvia Machine: System: Dell (portable) product: Vostro 1500 Mobo: Dell model: 0NX907 Bios: Dell v: A06 date: 04/21/2008 CPU: Dual core Intel Core2 Duo T5270 (-MCP-) speed/max: 1135/1401 MHz Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: email@example.com GLX Renderer: Mesa DRI Intel 965GM GLX Version: 2.1 Mesa 17.0.7 Network: Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44 Card-2: Broadcom BCM4311 802.11b/g WLAN driver: b43-pci-bridge Drives: HDD Total Size: 250.1GB (5.3% used) Info: Processes: 167 Uptime: 10:52 Memory: 1076.5/3936.1MB Client: Shell (bash) inxi: 2.2.35
After restarting these Open Mesh A60 APs, some of them don't work correctly and must be restarted again. Hence, my desire to force a connection to a specific AP and test its functionality.
 Use Default Font Size and Colors
"Please don't use coloured text"
 Use Images Sparingly
Shall I use a thousand words instead :-)
 Do Not Cross-Post
 Indicate Solved Topics
If there is a solution to be had. Perhaps another method of forcing a connection to a specif AP will be the solution, but it would be nice to know why my particular scheme failed.
Sorry for the long post, but the "How To Get Help!" post did as for "Details! Details! Details!".
Thanks in advance for your attention to this issue.