CAPs Manager

We were able to reproduce this problem. We will try to fix this problem in one of the next RouterOS releases.

Thanks Nick I will try tomorrow.

Hi Nick,

I tried:

[admin@CAPsMAN] /caps-man access-list> print detail
0 ;;; Deny all low signals
interface=all signal-range=-120..-60 action=reject

but no success. As per screen shot quite a few -60 to -120

Regards

Aidan
prtscrn.png

Today I saw load balancing group function. What will it do?

Interesting…
Mikrotik, can you tell us more about this feature…

Sorry to appear ignorant but this is fairly new to me.

I have been looking at upgrading from standalone AP’s to a managed AP environment for a while and was planning to use a CAPWAP based system (Cisci, Zyxel, Unifi(?) or similar) as this appears to be an industry standard. (Wikipedia states ‘The protocol specification is described in RFC 5415’)

Is CAPsMan based on the same protocols or do we have to use MikroTik equipment to gain this functionality?

Thanks
Matthew

Any ideas as to what the Load Balancing Group will do?

There is one feature missing in CAPsMAN (small but very important):
In WinBox and WebFig: Registration Table does not show comments from Access List. In Registration Table column “Comments” cannot be added. In terminal window comments are shown properly, so this is missing feature of WinBox and WebFig.

In old wireless package Registration Table was showing comments that were assigned to MAC addresses in Access List. Will this option be added to new wireless-fp?

We will try to add support for this.

Hi
it is possible to run eap in capsman? if so, how? I can not bite.
By the way I might add from each script that turns off the wifi on the night and on Sundays
capsEnable

:local date [/system clock get date]
:local result ""
:local months [:toarray "jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec"]
:local monthtbl [:toarray "0,3,3,6,1,4,6,2,5,0,3,5"]
:local daytbl [:toarray "sun,mon,tue,wed,thu,fri,sat"]
:local month [:pick $date 0 3]
:local day [:pick $date 4 6]
:local dayc [:pick $date 5 6]
:local century [:pick $date 7 9]
:local year [:pick $date 9 11]
:local yearc [:pick $date 10 11]
:if ([:pick $date 4 5] = 0) do={ :set day ($dayc)}
:if ([:pick $date 9 10] = 0) do=[:set year ($yearc)]
:local sum 0
:set sum ($sum + (2 * (3 - ($century - (($century / 4) * 4)))))
:set sum ($sum + ($year / 4))
:set sum ($sum + $year + $day)
:for mindex from=0 to=[:len $months] do={
  :if ([:pick $months $mindex] = $month) do={:set sum ($sum + [:pick $monthtbl $mindex]) }
}
:set sum ($sum - (($sum / 7) * 7))
:set result [:pick $daytbl $sum]
:if ($result != sun) do={/caps-man interface enable [/caps-man interface find disabled=yes]}

capsDisable

caps-man interface disable [/caps-man interface find disabled=no]

Does somebody tested seamless roaming in different cap modes? Does it work?
I’m just waiting for 2 baseboxes to come so I’ll test it soon. Just wanted to know if someone did it already.
Regards.

it will have few packet lost…

Any reviews on usage of Capsman in a semi/production deployment ? I need to do a wireless roll out for nearly site wide VOIP + Email connectivity in the not too distant future. I’d normally go to UBNT but their current stuff has left a really bad taste in my mouth.

Would be interested to know if any problems were encountered with roaming.

It’s sad. I hope at least it’s switching a little bit faster than without controller with PSK and significally faster with EAP.
Thanks for reply.

We have a CAPsMAN system (6.13) in production over here.
The manager runs on a 2011, ten BaseBox2 connected as CAPs. - CPU utilization around 20…35%.
Two SSIDs on two networks, both on manager forwarding.
Traffic is constantly around 20…30MBps with peaks up to 150MBit.
We have a few VoIP-Clients (Aastra AMC+ system on iPhones and Android) the roaming of which works quite well - but it strongly depends on the client. I noticed iPhones roaming slightly smoother than Android devices (HTC and Samsung). Moving around with an iPhone with an active VoIP call does not drop out at all whereas the same client on Android produces a short (feels like 100ms) dropout, but does not disconnect the call.
Non-VoIP access works perfectly.
Moving around pinging a device behind the CAPsMANager drops one packet every once in a while when roaming, but there also are occasions when I don’t see a single packet lost.

Hope, that helps.
-Chris

Thanks for the update cdiedrich.
Sounds very promising.

can describe your signal strenght range for clients ?

..and .how many clients (avg/peak) ? ..I’ve never seen that info in your msg

Client count is about 30 (Laptops, smartphones and BaseBox2 in client mode) in average, up to 200 (smartphones only) peak.
Kikoleg, I’ll collect some signal strength data tomorrow, but I know by heart the fewest of them are below -60.

Cheers
-Chris

cdierdrich I can send you an email directly to my question ?