-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Paul Julian Sent: Tuesday, 1 July 2014 8:16 PM To: public@talk.mikrotik.com.au Subject: [MT-AU Public] CAPSMan
Hi guys, I was wondering who has done some playing around with CAPSMan so far ??
We have a wireless network we need to build for a customer but they need a couple of AP's on the same SSID in reasonably close proximity which means they will interfere with each other. I was wondering, with the limited amount I have researched this new component, will it help in this situation and allow users to smoothly
from one AP to another ?
Previously we have worked with Ruckess wireless AP's and controllers and
Hi Paul, Like Russell already said, CAPsMAN works quite well for jobs that it is designed to do. Unfortunately, smooth transition between APs is not one of the things it is designed for. That was a surprise for me when I played around with the original release, because it was my assumption that this was precisely one of the reasons we need a wireless controller. Instead, what it does do (and does it well) is to offer a single interface for management of many wireless APs. CAPS manager can be on one of the APs or even on a router with no wireless. On the manager, it is possible to create 'configuration sets' where a set is made up of wireless properties (channel, protocol, etc) security profiles, and access/connection lists. You then assign the configuration set to one or more 'slave' APs, and then when you change the config on the master, it automatically updates the assigned slaves. This is great for maintaining wireless passwords for multiple APs or rolling out a new mac address to access lists throughout a group of APs. When I discovered that there was no function for hand-off between APs, I immediately asked MT direct. The reply I got was that this is functionally 'planned for future release' of CAPsMAN - but as per usual MT style, there is no estimated approximated or rumoured release date ;-) In the meantime, the most effective way I have found to deal with roaming client is to use 'access list' to set a minimum signal required to connect to the AP. What this does is to refuse connection from clients that are too far away (say -70dBm) and force the client to find a closer AP to connect to. You don't need CAPsMAN to do that, but when there are lots of APs, and you want to adjust those signal limits from time to time, CAPsMAN is very handy tool to do it! Hope this info helps (and not too disappointing! ;-) Cheers! Mike. transition they
seem to handle having AP's close to each other without any issues for users roaming, will CAPSMan help in situations like this as well ?
What approach would you take in this situation ?
Thanks Paul _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au