409      iPhone_iPad_Mac_apple

Force wifi to specific BBSID. (force 5ghz)

Hello,

I've been trying to find a solution for last two days about a problem I found using Yosemite on my Macbook Air.

I'm sometimes in conferences where there are a lot of people connected to the same router (which is probably the closest determined by every OS) and this router has the same name where ever you go in the building, so anywhere you go you get instant connected to it. Problem is that in conference rooms everyone seems to be connected to the same router which becomes really slow.

There I decided to think: What if I force my mac to connect to another router (others are not that far) maybe I will get a better connection and will not get my VPN disconnected every 5 minutes.

So I did search over the internet and first found the following commands:

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport --associate=XXX --bssid=YYY

xxx= SSID/network name    yyy= BSSID

The problem is that this command won't work on OS X versions before OS X 10.6, I get an error like (invalid command --associate)... (alright......)

So I found another guy who talked about forcing to connect to a specific canal using this command (let's start some annoying fixing ok..):

sudo /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport --channel=num

num= the canal number (ex: 6,  12, 1)

I did try that last one, without any success.

I'm currently at home, my ISP is Orange and we get a router that supports 2.4 and 5ghz at the same time on different canals but both use the same SSID/network name. When I get close to my router and restart wifi my mac will connect to 5ghz, but when I will go farer and get a -70 RSSI (or more) it will automatically connect to 2.4ghz.

Some people said that they contacted Apple support and this one said that there was no way to connect to connect to the BSSID you want, this is like that.

Can someone confirm?

What came in my mind is: Am I safe?

What annoys me on my macbook is that when I open it, it wakes up and immediately connect to Wifi routers I previously logged on, but ONLY using SSID (network name)!!!

(ex: I can connect to McDonalds public wifi hotspot from one place, if I go to another McDonald it will automatically connect to that one!)

So immediately you think: What if a hacker creates a fake wifi hotspot with name "Company XXX Wifi", my macbook will probably get connected to it (my company has no wifi password) and what if that hacker is rooting this hotspot to the real company one which gets internet/intranet, I will open safari and browse personal informations without even knowing I'm on the fake hotspot! and all my data will go clearly through the hacker)

I can understand it is easier to make it work this way, but what about enterprises?

Is there is a way first, to disable that insecure "auto-connect to known SSID" feature but BSSID instead? (even if it is spoof-able but it makes a layer of protection against hackers kiddies)

Or even to have to choose to connect back or not when you open your computer from sleep?

And of course: How the **** do you select a specific network that has the same name?!

You will find your answer to that question here

Unfortunately this doesn't answer my question at all, since it is way more complex.

BUMP!

Bump.

I'm floating in a sea of xfinitywifi hotspots but it seems the one I'm sitting closest to has the lousiest Internet speeds. In the rare situations my mac does connect to a different AP I get really great speeds (for what I need).

So yeah... a solution would be nice.

I have the same problem as Greg Holden. I would like to either:

1. block access points by BSSID, or
2. connect to a specific access point by BSSID

That way I would be empowered to choose the best xfinitiwifi hotspot. As it stands, the one closest to me has no internet connection at all, but OS X keeps connecting to it anyway.

@Leopardus There is no particular article at this link. The page is a hub for About.com. Your reply is not helpful.

You will find your answer to that question here . If you scroll down on that page, you will find an article how to connect to networks, Use Multiple Network Locations with your Mac, the principle that I use to connect in a big building with one of our deployments to connect to specific networks.

When used correctly, it will connect to the specific network every time, even with stronger signals present.

Ideally, one should start an own threat with your own problem.

HTH

Leo

Hi Leo, unfortunately, that doesn't resolve the problem we're facing. For vwssl, Greg, and myself, we're all facing the same concern: all the access points have the same SSID name. They run in both 2.4 GHz and 5 GHz so there isn't a way to differentiate speed by SSID name. In addition each access point has its own performance limitations based on the number of active connections and the download speed of the cable connection. In my case, its even more drastic because access point nearest to me broadcasts its SSID but the internet connection doesn't work at all.  We want to connect to a different access point by BSSID (MAC address) but can't figure out how to do that. Your link about locations seems like it would be good if you need to connect to a different SSID name. That doesn't work for us because all the access points have the same SSID. If I'm missing something from the link, please let me know.

Has anyone found a solution to this yet? Same exact problem: multiple APs (xfinitywifi) with the same SSIDs, some with better and faster signals than others, and I'd like to connect via BSSID.

You could try this open source solution:

https://github.com/qpSHiNqp/airport-bssid

Use google translate to check out.

In Nihongo (also a little propaganda)

Recent Mac airport command can not connect to AP with BSSID specification. qpSHiNqp the Interop Tokyo when had participated as STM in 2013, it has created a tool that can be Assoc in BSSID is specified because this it was troubled by the cause.

Interop Tokyo has a huge huge exhibition network called ShowNet and a huge number of APs used by visitors and exhibitors etc. are installed.These APs are blowing WiFi of several different policies Of course, things of the same policy are offered with the same ESSID (usually called SSID) ESSID is a type of hidden / encapsulation that allows users to use WiFi without being aware of individual AP settings Meanwhile, since the task of conducting the connectivity test at the individual AP level also occurs as in the case of the network construction unit, the Association at the BSSID level is carried out from the relation between the AP and the BSSID obtained beforehand It is desirable that communication checking is possible at the AP level.

From such circumstances, I raised the tools I made in 2013 to github, but for some time over the past few months, issue reports from foreign users got up and finally the network construction period of Interop Tokyo 2016 also started I thought that I will maintain it for a long time, so I think that there are incomplete parts, but if you find a bug, please report Issue, if you like it, Star will be my best pleasure, especially , Issue report from Makuhari group responds as much as possible on the same day. Please do your best this year as well.

Thanks, rccharles. I found this independently and downloaded it, but it didn't work in Sierra. Bummer, too, as it would have been the perfect solution.

Thanks for the feedback.

If I'm missing something from the link, please let me know.

The author is accepting feedback.

R

By the way, what did you do to try out the tool?  The readme files is a repeat of what is in the git page.

Do I need to compile the command?

What folder is the command in?

I looked at the source, it's only 115 lines long.

R

I didn't compile it; I ran it in a terminal window.

Run terminal, navigate to the directory in which you placed the files, then type ./airport-bssid eth0 <paste in BSSID>

For example:

1. I downloaded the files to: /Users/<username>/Desktop/personal/airport-bssid-master
2. The executable is in the Build directory, so: /Users/<username>/Desktop/personal/airport-bssid-master/Build
3. Then: ./airport-bssid eth0 <paste in BSSID>

I was able to get the BSSID by:

1. Option+Clicking on the wifi icon in the toolbar
2. Click on "Open Wireless Diagnostics"
3. Ignore the window that appears
4. Go to the Window menu, choose Scan
5. In that window, find the BSSID that you want and type that into the command line, like: ./airport-bssid eth0 aa:bb:cc:dd:ee:ff

Running the command does something, but it didn't magically associate with the AP associated with the BSSID. Disabling and re-enabling wifi did do something, in that it temporarily attached to the proper AP, but then it crapped out. You might investigate that line of thought (running the command, disable, reenable).

最后更新：2017-09-23 02:43:45

  上一篇： Time & Date Preference Pane

  下一篇： anybody know what eoptcron is?