Is it possible for CAPsMan APs to still provide support for using the WPS button? If not, enabling WPS on a caps configuration would be really useful for a project I’m working on. Master configuration only would be fine, though the ability to specify it to work on a slave configuration could be useful too (I understand it would probably only be able to work for one or the other at any given time).
Since I can’t see anything that indicates this currently works, I’ll assume this is then a feature request and I’ll describe how I think it should function…
On CAPsMan Configuration profile a WPS support option is added, During the provisioning phase the AP determines which interfaces will support the WPS button and which do not (aka master configuration vs slave configuration, enabled or disabled), then when someone presses the WPS button the AP registers on the CAPsMan the press, much like pressing the WPS button in the webfig works in a stand alone AP setup, and the CAP then performs the WPS handshake with any devices connected to that AP, but only to the AP the button was pressed on (aka pressing the WPS button on one AP will NOT trigger the WPS process for a client connected to an interface attached to any other AP in the building).
And to anyone thinking about why would users even be able to access the WPS button on the AP in a CAPsMan deployment, or how would this possibly be useful, you are thinking far to much inside the box about how to use CAPsMan… I should be announcing the details of this new project in the next 3-5 weeks, and while I’m sure MikroTik won’t have this feature completed by then, I assure you this feature will be very useful!
I need this function, too. I have to deploy a wireless system where normal customers use Hotspot and staff uses regular AP (different limitations in time, speed and surfing). Staff changes everyday and needs to pair quickly with the AP. I cannot give the password in order to avoid that staff people give it to other staff people (I decide who can access and who don’t).
WPS is the answer and a WEB API button is the way.
Mikrotik staff, please, give us updates: why AP has WPS and CAP doesn’t?
Do you understand that WPS is just a ways to automagically tell the client device what the password is. You are not telling the password to your staff, but you still transfer it to their client devices. It’s trivial then to get that stored password on Windows devices. I also believe it’s possible to get the stored WiFi passwords on rooted Android devices.
Sure, I understand. I understand that a device cannot join a wireless network without storing password, too. Don’t you think?
Well, we cannot avoid to store wireless passwords to devices, let’s go ahead!
You have to consider the mean-user. I don’t want to give the password to a mean-user, giving it to a mean-device instead.
Do you know a better way than WPS? Just indicate it to me, please!
My focus is to avoid wasting internet band, so if I get a motu-user that with a rooted smartphone can get the password, well, let’s let him surf the internet. He gained that!
But he will remain a single user, not all mean-users, not everyone. Once he will be logged in, he’ll find other countermeasures I’ll implemented.
Now we can discuss about the probability we’ll have in finding a newtork-motu waitress in a fast-food international chain staff.
