Page 1 of 1

CAPsMAN v2 ready for testing

Posted: Thu Nov 06, 2014 3:11 pm
by uldis
We have CAPsMAN v2 ready for testing.

Note: CAPsMAN v2 is NOT compatible with current CAPsMAN v1 (CAPsMAN v1 CAP devices will not be able to connect to CAPsMAN v2 and CAPsMAN v2 CAP devices will not be able to connect to CAPsMAN v1). It means that both CAPsMAN and CAP devices should have wireless-cm2 package installed in order to make CAPsMAN v2 system to work.
If you want to try out the CAPsMAN v2 upgrade all the CAPs and the CAPsMAN to latest RouterOS version and install wireless-cm2 package.

CAPsMAN v2 features:
* CAPsMAN automatic upgrade of all CAP clients (configurable)
* improved CAP<->CAPsMAN data connection protocol
* added "Name Format" and "Name Prefix" setting for Provision rules
* improved logging entries when client roams between the CAPs
* added L2 Path MTU discovery

Upgrade options from v1 to v2:

Option1: Install a new temporary CAPsMAN v2 router in same network where the current CAPsMAN router is and start upgrading CAPs with wireless-cm2 package. All CAPs with the v2 will connect to the new temporary CAPsMAN v2 router. After every CAP is upgraded to v2, upgrade your current CAPsMAN to v2 and then turn off the temporary CAPsMAN v2 router.

Option2: Upgrade your CAPs and then CAPsMAN to v2 at the same time. In this case you could have little more downtime unless you schedule all the CAPs to reboot/install at the same time.

Wireless-cm2 package can be downloaded from the Mikrotik download page under release candidate:
http://www.mikrotik.com/download

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 1:43 am
by indnti
It's great that one can upgrade the caps now!
But how is the upgrade and package-path configured? Have I upload the packages to "files" manually?

/caps-man> manager print
enabled: yes
certificate: none
ca-certificate: none
package-path:
upgrade-policy: suggest-same-version
require-peer-certificate: no

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 2:17 am
by slackR
CAPsMAN is getting better and better! We can now manage hundreds of access points with ease.

I would like to see more options available in CAPsMAN configurations like:
NV2 with encryption
Management Frame Protection
Remote Scanning, Freq. Usage, Snooper
WMM Support

Also, the interface naming format is great and I would like to suggest another field.
I think prefix identity and SSID would be awesome. What do you think?

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 10:35 am
by indnti
Please can someone tell how to configure the "package-path" and how the upload of a packag take place

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 10:46 am
by uldis
Please can someone tell how to configure the "package-path" and how the upload of a packag take place
For example specify such info: "package-path: /nova"

And then upload files to the nova folder
[uldis@CAPsMAN] /file> print
 # NAME                   TYPE                        SIZE CREATION-TIME       
 0 nova                   directory                        nov/05/2014 12:17:47
 1 nova/wireless-cm2-6... package                 884.1KiB nov/05/2014 12:17:43
 2 nova/routeros-mipsb... package                   9.7MiB nov/05/2014 12:17:48
Also note that you will need to wait till the RouterOS v6.22rc8 till you could test the upgrade feature as to make the CAP to connect it should have v6.22rc7 already.

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 1:00 pm
by TikUser
So, now there are 3 wireless packages:
wireless,
wireless-fp,
wireless-cm2.

What will happen with the wireless-fp package? Will it be discontinued?

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 1:24 pm
by JaJ0s
Very interesting, could someone share info about how this "improved logging entries when client roams between the CAPs"
works? (ex. ping losses).

Peter

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 3:27 pm
by uldis
Very interesting, could someone share info about how this "improved logging entries when client roams between the CAPs"
works? (ex. ping losses).

Peter
You will see such entrie in the log file when the client connects/roams to some other CAP:
15:20:44 caps,info 00:00:00:00:00:00@cap1 disconnected, registered to other interface

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 4:16 pm
by NathanA
Why cannot v1 CAPs connect to v2 CAPsMAN or vice-versa? Aren't CAPsMAN v1 and v2 both RFC5416 (CAPWAP) compliant?

-- Nathan

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 4:29 pm
by honzam
So, now there are 3 wireless packages:
wireless,
wireless-fp,
wireless-cm2.

What will happen with the wireless-fp package? Will it be discontinued?

Any info about it? Have you plan merge this packages?

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 5:01 pm
by Lakis

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 5:46 pm
by slackR

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 07, 2014 5:55 pm
by uldis
Why cannot v1 CAPs connect to v2 CAPsMAN or vice-versa? Aren't CAPsMAN v1 and v2 both RFC5416 (CAPWAP) compliant?

-- Nathan
CAPsMAN v2 is not capwap compliant due to limitations of capwap protocol.

Re: CAPsMAN v2 ready for testing

Posted: Sat Nov 08, 2014 11:22 pm
by boen_robot
Why cannot v1 CAPs connect to v2 CAPsMAN or vice-versa? Aren't CAPsMAN v1 and v2 both RFC5416 (CAPWAP) compliant?

-- Nathan
CAPsMAN v2 is not capwap compliant due to limitations of capwap protocol.
But then, if CAPsMAN v1 was, shouldn't you perhaps call this one something different? Like "MTCAPsMAN" for example.

I mean, what if CAPWAP gets a revision (let's call it tentatively CAPWAP.Next) that doesn't have those limitations while still being compatible with the current CAPWAP protocol? You make CAPsMAN v3 which is not compatible with v2, but is compatible with v1, because v3 is CAPWAP.Next compliant, while v2 is not?

Re: CAPsMAN v2 ready for testing

Posted: Sun Nov 09, 2014 12:13 pm
by TonyJr
I have a recommendation for the next release - check provisioning configuration for corrupt or invalid settings and advise user when upgrading. I had to remove and add a provisioning rule which became corrupt, but it looked normal from the cli and winbox.
If not for upgrade, maybe a button to check for any settings marked as invalid or e.g. Rule with interface configured that does not exist any more. Important to check even the disabled settings and the entire device.

Re: CAPsMAN v2 ready for testing

Posted: Sun Nov 09, 2014 12:18 pm
by TonyJr
I am able to finally install capsman2 on a rb493g and enable cap on it and set capsman option to 127.0.0.1 . (use capsman2 on a cap itself)

One bug I can see is that registered clients show TX of -1 in winbox.



Would it be possible to see CCQ in winbox for registered clients?



Tony

Re: CAPsMAN v2 ready for testing

Posted: Sun Nov 09, 2014 9:44 pm
by TonyJr
Hello,

I would like to propose the following; An option in radio and an option in provisioning profile which can over-ride the main cap upgrade rule.

Two reasons for this:

- Having capsman2 and cap on the same routerboard, to prevent reboot of the controller when new software is uploaded.

- More granular control over software updates.

Another feature would be for setting software upgrade policy to none, but in the section that lists registered CAPs, have a button to upgrade the device. This could also be done for profiles to apply upgrade to CAPs using the profile selected, or groups of CAPs if groups get implemented.

TonyJr

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 10, 2014 1:59 am
by lunchboxrts
Another feature:
The ability to have groups of radio mac address for provisioning. For example, so i can groups of radios for extension channels, some get eC eCee, some get Ce eeCe etc

Re: CAPsMAN v2 ready for testing

Posted: Wed Nov 12, 2014 3:36 am
by uldis
I have a recommendation for the next release - check provisioning configuration for corrupt or invalid settings and advise user when upgrading. I had to remove and add a provisioning rule which became corrupt, but it looked normal from the cli and winbox.
If not for upgrade, maybe a button to check for any settings marked as invalid or e.g. Rule with interface configured that does not exist any more. Important to check even the disabled settings and the entire device.
we are not aware of such bug Could you tell us more detailed what exactly stopped working with the provision rules?

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 14, 2014 3:11 pm
by wenasong
For some reason, based on 6.22rc7 and 6.22final both the provisioning feature did not provision random channels, it only provision the lowest channel available of the country-settings.

Re: CAPsMAN v2 ready for testing

Posted: Sat Nov 15, 2014 4:21 pm
by nuru
Is this feature requested available now http://forum.mikrotik.com/viewtopic.php?f=7&t=85974

Re: CAPsMAN v2 ready for testing

Posted: Sat Nov 15, 2014 6:27 pm
by nuru
Indeed there is a lot of improvement. 4 BaseBox2 with RB750 as the CAPsMAN Will test the roaming and see how it it hands of.

Re: CAPsMAN v2 ready for testing

Posted: Sat Nov 15, 2014 7:59 pm
by uldis
For some reason, based on 6.22rc7 and 6.22final both the provisioning feature did not provision random channels, it only provision the lowest channel available of the country-settings.
Most likely the lowest channel is the least used in that area.

Re: CAPsMAN v2 ready for testing

Posted: Sat Nov 15, 2014 8:01 pm
by uldis
Is this feature requested available now http://forum.mikrotik.com/viewtopic.php?f=7&t=85974
in registration table you can already see the rx and tx statistics for each mac address.

Re: CAPsMAN v2 ready for testing

Posted: Sat Nov 15, 2014 8:34 pm
by nuru
Is this feature requested available now http://forum.mikrotik.com/viewtopic.php?f=7&t=85974
in registration table you can already see the rx and tx statistics for each mac address.
Sorry didnt check. Hopefully we will get CCQ soon?

Re: CAPsMAN v2 ready for testing

Posted: Sun Nov 16, 2014 5:13 am
by newkirk
I have a 951G-2HnD and a cAP2n both running 6.22.

I downloaded wireless-cm2-6.22-misbe.npk and pushed it to both devices.

The 951G happily installed the package.

The cAP2n ignores it.

What did I miss?

j

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 17, 2014 3:03 am
by parinya1957
Is auto channel support on this V2?

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 17, 2014 3:08 am
by nz_monkey
Is auto channel support on this V2?
From my testing on v2 all AP's end up on channel1

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 17, 2014 11:06 am
by ivugrinec
There is a bug in 6.22. Auto select frequency on CAPsMAN v2 does NOT work.

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 17, 2014 11:07 am
by ivugrinec
I have a 951G-2HnD and a cAP2n both running 6.22.

I downloaded wireless-cm2-6.22-misbe.npk and pushed it to both devices.

The 951G happily installed the package.

The cAP2n ignores it.

What did I miss?

j
Did you enable CAP on a wireless interface?

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 17, 2014 3:19 pm
by TonyJr
I have a recommendation for the next release - check provisioning configuration for corrupt or invalid settings and advise user when upgrading. I had to remove and add a provisioning rule which became corrupt, but it looked normal from the cli and winbox.
If not for upgrade, maybe a button to check for any settings marked as invalid or e.g. Rule with interface configured that does not exist any more. Important to check even the disabled settings and the entire device.
we are not aware of such bug Could you tell us more detailed what exactly stopped working with the provision rules?
Hello, I have looked further into this, and it looks like the cause of the problem was a backup file for a different model being restored to this device, which corrupted lots of settings and filled the storage with many random folders in web-proxy causing 100% cpu. Upon resetting to the correct backup file, all is OK. Typical user error!

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 17, 2014 6:45 pm
by newkirk
I have a 951G-2HnD and a cAP2n both running 6.22.

I downloaded wireless-cm2-6.22-misbe.npk and pushed it to both devices.

The 951G happily installed the package.

The cAP2n ignores it.

What did I miss?

j
Did you enable CAP on a wireless interface?
Yes, everything was already set up and working with CAPsMAN1. The problem is that I cannot get the cAP2n to install the package. Pushed the file to both devices, rebooted both. 951G has the new package installed after reboot and has removed the file, the cAP2n has NOT installed the package and the file remains.

j

Re: CAPsMAN v2 ready for testing

Posted: Thu Nov 20, 2014 1:10 pm
by redbullsteve
Hi,

It would appear the auto channel feature is broken in v2,

I have tested it in a clean environment with 10+ AP's all on channel 1 and used CAPsMANv2 to deploy 3 AP's and they all loaded using Channel 1.

If you look at the current stat of the CAP while you disable and enable it flicks to selecting-channel for a ms and always loads channel 1

Can anyone else confirm the auto-channel is broken in v2?

I have just loaded the latest version 6.23rc2 and get the same results, but the version control in CAPsMANv2 works well :)

Steve

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 21, 2014 1:20 am
by pizzulicchio
i'm not be able to set the extension channel using CAPsMan v2.
I can only set the channel using 20Mhz.
If i set 40 mhz stops working with the error

"unsupported channel"

What is wrong?

is it a know issue?

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 24, 2014 12:42 pm
by izytech
Are there any plans for Nv2 support in CAPsMAN?

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 24, 2014 12:44 pm
by normis
Are there any plans for Nv2 support in CAPsMAN?
CAPsMAN is mostly meant for managing of access points in hotels, homes, apartments, offices etc. the clients in these places are windows and mac laptops, phones etc.

Nv2 is only for RouterOS. Usually RouterOS devices are not so many in such small area, that they would need to be managed in such way.

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 24, 2014 5:55 pm
by uldis
i'm not be able to set the extension channel using CAPsMan v2.
I can only set the channel using 20Mhz.
If i set 40 mhz stops working with the error

"unsupported channel"

What is wrong?

is it a know issue?
Specify width 20 and then specify the extension-chaneel option to get the 20/40mhz option.

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 24, 2014 5:57 pm
by uldis
newkirk, try to place the wireless-cm2 package in the root directory and not the flash directory.
Also check the log file after the reboot why it didn't install it.

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 24, 2014 6:24 pm
by redbullsteve
Hi,

It would appear the auto channel feature is broken in v2,

I have tested it in a clean environment with 10+ AP's all on channel 1 and used CAPsMANv2 to deploy 3 AP's and they all loaded using Channel 1.

If you look at the current stat of the CAP while you disable and enable it flicks to selecting-channel for a ms and always loads channel 1

Can anyone else confirm the auto-channel is broken in v2?

I have just loaded the latest version 6.23rc2 and get the same results, but the version control in CAPsMANv2 works well :)

Steve

Any comment on the above issue, Auto Channel not working in CAPsMAN v2?

Steve

Re: CAPsMAN v2 ready for testing

Posted: Thu Nov 27, 2014 3:01 pm
by uldis
redbullsteve, please upgrade the RouterOS to v6.23rc8 where the Auto frequency option is working for CAPsMAN v2.

Re: CAPsMAN v2 ready for testing

Posted: Thu Nov 27, 2014 3:26 pm
by pizzulicchio
oook!!
thank yoy uldis!

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 28, 2014 12:45 pm
by redbullsteve
redbullsteve, please upgrade the RouterOS to v6.23rc8 where the Auto frequency option is working for CAPsMAN v2.

Excellent, Have just upgraded and can confirm auto channel is again working :)

Re: CAPsMAN v2 ready for testing

Posted: Sun Nov 30, 2014 6:12 pm
by gem
Are you planning to add the management of these features by Wirless Advanced Settings - disconnect-timeout and on-dail-retry-time?

Re: CAPsMAN v2 ready for testing

Posted: Mon Dec 01, 2014 11:03 pm
by Petr42
Hi,

after upgrade to 6.22 and CAPsMAN v2 I have problem with virtual APs, I am not able to connect to them. When I moved vAP cfg to primary AP on the same HW, it works immediately - so it should be ok from cfg perspective. RB922UAGS-5HPacD+R11e-2HPnD and RB951G-2HnD, CAPsMAN running on different HW. All 6.22.

Anybody else with the same behaviour?

Thx.

Re: CAPsMAN v2 ready for testing

Posted: Tue Dec 02, 2014 10:16 am
by uldis
Hi,

after upgrade to 6.22 and CAPsMAN v2 I have problem with virtual APs, I am not able to connect to them. When I moved vAP cfg to primary AP on the same HW, it works immediately - so it should be ok from cfg perspective. RB922UAGS-5HPacD+R11e-2HPnD and RB951G-2HnD, CAPsMAN running on different HW. All 6.22.

Anybody else with the same behaviour?

Thx.
Please upgrade the CAPsMAN v2 to RouterOS v6.23rc10 and check again.
You use local or full forwarding?

Re: CAPsMAN v2 ready for testing

Posted: Tue Dec 02, 2014 8:43 pm
by Petr42
Hi,

after upgrade to 6.22 and CAPsMAN v2 I have problem with virtual APs, I am not able to connect to them. When I moved vAP cfg to primary AP on the same HW, it works immediately - so it should be ok from cfg perspective. RB922UAGS-5HPacD+R11e-2HPnD and RB951G-2HnD, CAPsMAN running on different HW. All 6.22.

Anybody else with the same behaviour?

Thx.
Please upgrade the CAPsMAN v2 to RouterOS v6.23rc10 and check again.
You use local or full forwarding?
Local forwarding.

Is upgrade needed on both CAP and CAPsMAN?

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 04, 2014 4:05 pm
by uldis
you need to upgrade both CAPsMAN and CAP boards to wireless-cm2 package.

Re: CAPsMAN v2 ready for testing

Posted: Fri Dec 05, 2014 6:38 pm
by Petr42
you need to upgrade both CAPsMAN and CAP boards to wireless-cm2 package.
This is clear, question was related to version upgrade of cm2 package. I.e. which of them is important in this case? Both?

Ad 6.23 released: it is not working as well.
  • RB850Gx2 as CAPsMAN
  • RB951G-2HnD as CAP
  • RB922UAGS-5HPacD + R11e-2HPnD as CAP (dual-radio)
EDIT: Seems to be problem with CAPsMAN v1 as well. I moved cfg to RB951 - no change, swapped there CAPsMAN from v2 to v1 - no change, moved there cfg from vAP to primary i/f and cfg works immediately. The error is clients are not able to connect, probably due to auth error. No log records on CAP nor CAPsMAN - there is no record about such attempt (s).

Re: CAPsMAN v2 ready for testing

Posted: Mon Dec 08, 2014 11:56 am
by uldis
Petr42, please make a support output file when this problem is happening on the CAPsMAN and CAP and send to support@mikrotik.com
Make sure that you are using CAPsMAN v2 packages from v6.23.
Also tell us what configuration you use so we could try to reproduce it.

Re: CAPsMAN v2 ready for testing

Posted: Wed Dec 10, 2014 12:18 am
by bleblas
CAPsMAN is mostly meant for managing of access points in hotels, homes, apartments, offices etc. the clients in these places are windows and mac laptops, phones etc. 
I thing, you need more work about fast roaming in capsman 2

Wifi device need to lost of signal on cap1 to connect another cap2, but wifi device can work long time with cap1 on signal -89 even the cap2 is closer with signal -40

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Wed Dec 10, 2014 1:02 am
by jarda
You should set roaming functionality on the clients to the more aggressive option.

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 12:17 am
by ebreyit
In multi-AP installations I've also been using the following to assist in nudging clients onto AP's whilst moving around.
In most scenarios it works great. Some applications might suffer from the sudden drop off though (VOIP).
Streaming has worked fine for me whilst jumping from one AP to another. Play with the signal ranges to find what works best.
/caps-man access-list
add action=accept client-to-client-forwarding=yes interface=all signal-range=-80..120
add action=reject interface=all signal-range=-120..-81

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 9:51 am
by bleblas
Re

yes i use access list but access list work only when client connecting to AP, not when it is connected and then signal making worses.

i use access list
/caps-man access-list
add action=accept client-to-client-forwarding=yes interface=all signal-range=-80..120
add action=reject interface=all signal-range=-120..-81
and write some script to kick client with bed signal
    
:local MAXsignal "-78";
    :local capsClientId;
    :local capsClient;
    :local capsClientSignal;

    :foreach i in=[/caps-man registration-table find] do={

    :set capsClientId [/caps-man registration-table get $i];
    :set capsClient [/caps-man registration-table get $i mac-address];
    :set capsClientSignal [/caps-man registration-table get $i rx-signal];

    :if ("$MAXsignal" > $capsClientSignal) do={
    /caps-man registration-table remove $i;
    :log info "Caps script kick user $capsClient signal $capsClientSignal";
    }
    }
but it's not work perfect, some https session make disconnect and need re-logon and some business applications too

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 10:03 am
by ebreyit
Hi bleblas

My experience is that if set correctly Access List will disconnect an existing client if signal drop below threshold if set correctly as per Wiki

You should be seeing log entries stating that a client has disconnected, signal too weak!
I then see it immediately register on the next AP (if there is one to goto)


http://wiki.mikrotik.com/wiki/Manual:In ... ccess_List
Warning: If there is no entry in ACL about client which connects to AP (wireless,debug wlan2: A0:0B:BA:D7:4D:B2 not in local ACL, by default accept), then ACL for this client is ignored during all connection time.

For example, if client's signal during connection is -41 and we have ACL rule

/interface wireless access-list
add authentication=no forwarding=no interface=wlan2 signal-range=..-55
Then connection is not matched to any ACL rule and if signal drops to -70..-80, client will not be disconnected.


To make it work correctly it is required that client is matched by any of ACL rules.

If we modify ACL rules in previous example to:

/interface wireless access-list
add interface=wlan2 signal-range=-55
add authentication=no forwarding=no interface=wlan2 signal-range=..-56
Then if signal drops to -56, client will be disconnected.

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 10:19 am
by bleblas
hi ebreyit

no way, i test it on 6.23 capsman v2 9-12-2014 , and access list works only when you connecting ..
and faster testet on capsman 1 on 6.22,6.23-rc

add access list
add action=reject interface=all signal-range=-120..-70
connect with good signal 120..-60 and then go away then signal go to -76 and worses

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 10:32 am
by ebreyit
Hi bleblas,
If that is your only access list rule then it's not complete.

As per the wiki and my code example you need to include an accepting rule first so that the client is included in the connected clients ACL, once there it can then be controlled by further rules which will disconnect clients when the signal drops too low.

I have this running on a couple of networks al now using 6.23 and all working as expected


/caps-man access-list
add action=accept client-to-client-forwarding=yes interface=all signal-range=-80..120
add action=reject interface=all signal-range=-120..-81
hi ebreyit

no way, i test it on 6.23 capsman v2 9-12-2014 , and access list works only when you connecting ..
and faster testet on capsman 1 on 6.22,6.23-rc

add access list
add action=reject interface=all signal-range=-120..-70
connect with good signal 120..-60 and then go away then signal go to -76 and worses

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 10:37 am
by bleblas
re

i have access rule but it was secend, i change to first accept and then reject and check.

thx

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Thu Dec 11, 2014 10:40 am
by ebreyit
Great, that should work for you once switched as the list operates top to bottom.

re

i have access rule but it was secend, i change to first accept and then reject and check.

thx

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Sat Dec 13, 2014 12:48 am
by bleblas
Hello

Today i test this configuratins of access list and it is work nice

It's disconnect with week signal

Thx for help

Bleblas

Re: CAPsMAN v2 ready for testing

Posted: Sat Dec 27, 2014 11:10 am
by hadyatef
Hi All
As I have a project need 55 Access points controlled by Access point controller
i like to do it with CAPsMAN facility of mikrotik RouterBOARD
my question is which is the suitable Access point can i use in my project?
I read something about a new Mikrotik APs is that true ? is it efficient?
can i use any of TP-Link products ? which kind?

Re: CAPsMAN v2 ready for testing

Posted: Sat Dec 27, 2014 12:38 pm
by nuru
hadyatef.
TP-Link can only work as a normal CPE in a Mikrotik CAPsMAN configured network.
The AP (CAPs) you can use for Mikrotik WLAN controller (CAPsMAN) has to be a RouterOS powered AP, but you will want to use Mikrotik AP for compatibility reasons.
The space you want to cover will usually determine the type of AP you want to use.
For the WLAN controller (CAPsMAN), almost any Mikrotik router can be used as the WLAN controller, but you need to consider the CPU and memory of the router because that will determine the numbers of AP (CAPs). CPE, user and traffic that the WLAN controller will be able to handle.
Another thing to note is all Mikrotik device must have a post 6.14 RouterOS but you will want to go for the latest RouterOS, there has been a lot of improvement and bug fixes after 6.15. Remember also that CAPsMAN V1 is not compatible to CAPsMAN V2.

Hope this help

Re: CAPsMAN v2 ready for testing

Posted: Sat Dec 27, 2014 7:29 pm
by hadyatef
hadyatef.
TP-Link can only work as a normal CPE in a Mikrotik CAPsMAN configured network.
The AP (CAPs) you can use for Mikrotik WLAN controller (CAPsMAN) has to be a RouterOS powered AP, but you will want to use Mikrotik AP for compatibility reasons.
The space you want to cover will usually determine the type of AP you want to use.
For the WLAN controller (CAPsMAN), almost any Mikrotik router can be used as the WLAN controller, but you need to consider the CPU and memory of the router because that will determine the numbers of AP (CAPs). CPE, user and traffic that the WLAN controller will be able to handle.
Another thing to note is all Mikrotik device must have a post 6.14 RouterOS but you will want to go for the latest RouterOS, there has been a lot of improvement and bug fixes after 6.15. Remember also that CAPsMAN V1 is not compatible to CAPsMAN V2.

Hope this help
nuru
thx for yr repky
you put ne in the right way
can you give a recommendation of MT AP types you suggest

Re: CAPsMAN v2 ready for testing

Posted: Sun Dec 28, 2014 10:44 am
by nuru
hadyatef.
TP-Link can only work as a normal CPE in a Mikrotik CAPsMAN configured network.
The AP (CAPs) you can use for Mikrotik WLAN controller (CAPsMAN) has to be a RouterOS powered AP, but you will want to use Mikrotik AP for compatibility reasons.
The space you want to cover will usually determine the type of AP you want to use.
For the WLAN controller (CAPsMAN), almost any Mikrotik router can be used as the WLAN controller, but you need to consider the CPU and memory of the router because that will determine the numbers of AP (CAPs). CPE, user and traffic that the WLAN controller will be able to handle.
Another thing to note is all Mikrotik device must have a post 6.14 RouterOS but you will want to go for the latest RouterOS, there has been a lot of improvement and bug fixes after 6.15. Remember also that CAPsMAN V1 is not compatible to CAPsMAN V2.

Hope this help
nuru
thx for yr repky
you put ne in the right way
can you give a recommendation of MT AP types you suggest
Like I said before, a lot of things will determine what type of AP you want to use. About all Mikrotik AP will do, as long as it has the right RouterOS version.
Is the area you want to cover a close space or an open space?
What is the nature of obstruction along the signal propagation path?
How far are your CPE or client from the AP?
What bandwidth are you looking at?
I use Basebox 2 & Basebox 5`with Ubiquiti Airmax antenna for Outdoor open space. The Ubiquiti Antenna are quite pricey, you may want to use Mikrotik AP with SISO that requires cheaper antenna, but will lack the performance, signal quality and bandwidth of a MiMo systems.
And RB951 for indoor. Just bought some cAP 2n about two weeks ago but not installed yet.

Nurudeen

Re: CAPsMAN v2 ready for testing

Posted: Wed Dec 31, 2014 6:28 pm
by avenn
Hi,

Currently getting to grips with CAPsMAN2.

I've been experimenting with channel allocation and setting them to "auto" / blank.

At the moment the auto frequency option selects any channel (1 to 11) and this can lead to AP channel overlap (using 20 MHz channels). It appears as though as long as there is no overlap/interference with the 5 MHz centralish channel it will allocate the next one along.

Therefore in the 2GHz frequency range I only want the auto frequency to select from channels 1, 6 and 11.

From memory I need to create a scan-list that includes 2412, 2437, 2462. I expect this to prevent the overlap problem - to an extent.

However in CAPsMAN2 I don't seem to be able to choose scan list is an option?

Is this not a feature? Perhaps I'm looking at it from the wrong angle?

Can anyone help?

Regards

Aidan

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 02, 2015 7:31 pm
by redbullsteve
Hi,

Currently getting to grips with CAPsMAN2.

I've been experimenting with channel allocation and setting them to "auto" / blank.

At the moment the auto frequency option selects any channel (1 to 11) and this can lead to AP channel overlap (using 20 MHz channels). It appears as though as long as there is no overlap/interference with the 5 MHz centralish channel it will allocate the next one along.

Therefore in the 2GHz frequency range I only want the auto frequency to select from channels 1, 6 and 11.

From memory I need to create a scan-list that includes 2412, 2437, 2462. I expect this to prevent the overlap problem - to an extent.

However in CAPsMAN2 I don't seem to be able to choose scan list is an option?

Is this not a feature? Perhaps I'm looking at it from the wrong angle?

Can anyone help?

Regards

Aidan
This is a feature that I think needs to be added, I have the same problem, I raised it a while ago but Mikrotik don't seem to understand the requirement and think the way it is currently implemented is the way forward.

I want to be able to select the channels used as per the scan list.

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 02, 2015 11:37 pm
by avenn
hi redbullsteve,

thanks for reply.

that's a shame and disappointing. I would consider this to be a regression not progression.

perhaps they will add it later and just forget to tell us!

Regards

Aidan

Re: CAPsMAN v2 ready for testing

Posted: Sun Jan 11, 2015 10:34 am
by Zwodka
Hi All!

When I add a new Interface there are two MAC: "mac-address" and "radio-mac".
What is the difference?

Z,

Re: CAPsMAN v2 ready for testing

Posted: Sun Jan 11, 2015 5:20 pm
by 22hn
Feature request

On CAPsMAN "Registration Table" tab, I would like to have a column for CAP identity and SSID.

EDIT: Found out that SSID is only missing in winbox 3...! In the older version it's there...!

Re: CAPsMAN v2 ready for testing

Posted: Mon Jan 12, 2015 10:28 am
by Lansman
Wireless-cm2 package can be downloaded from the Mikrotik download page under release candidate:
http://www.mikrotik.com/download[/quote]

Sorry. I have been looking for a package called Capsman, or wireless-cm2, or anthing else that might be it.

Where do I find it? I seem to have found one for PPC, but the computer is a Routerboard. wireless-cm2-6.25rc5-ppc.npk Will that work in a Routerboard? I guess I sometimes just do not get it.

Re: CAPsMAN v2 ready for testing

Posted: Mon Jan 12, 2015 10:31 am
by normis
Here it is:
Screenshot 2015-01-12 10.30.31.png
PPC is a type of RouterBOARD. You must choose the appropriate system type, MIPS or PPC or other

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 13, 2015 10:41 am
by Lansman
Thank you. Oh... stupid me... one extra click did it. :? Thank you.

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 20, 2015 7:26 am
by chechito
to improve roaming and client behavior its very important the ability to control datarate set

the day capsman can do it the results will be much better.

acl method its very imprecise

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 20, 2015 8:22 pm
by IPANetEngineer
Just curious how many APs CAPsMAN is designed to support? How many have been tested by MT?

Re: CAPsMAN v2 ready for testing

Posted: Wed Jan 21, 2015 1:22 pm
by uldis
we have seen customers that manage more then 600 cap interfaces on one CAPsMAN.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 22, 2015 5:06 am
by lunchboxrts
Having a serious issue with capsman v2. radios are rb912's running the current version 6.25(started with the first beta of v2). we have carts of hp stream 11 with realtek wireless cards, when more than ~10-15 connect to a single access point the throughput drops to almost nothing and the client begin to drop off. this happens without transferring data just connected. when i disable capsman and run the ap unmanaged the issue mostly goes away. the client chipset is rtl8723be, i know your going to say its the realtek but this does not happen on my meraki ap's(trying to get away from meraki)

The capsman controller is a ccr1009 and caps devices are running in local forwarding mode. it appears that the capsman is having an issue with the keeping up with the clients.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 22, 2015 10:11 am
by uldis
please make a support output file from CAPsMAN and that CAP when you see this problem and then send them to support@mikrotik.com
Also provide what wireless configuration you use when you do not use CAP.

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 23, 2015 1:20 am
by IPANetEngineer
we have seen customers that manage more then 600 cap interfaces on one CAPsMAN.
That's great...what platform were they using for the CAPsMAN?

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 23, 2015 4:51 pm
by uldis
If I remember correctly than it was CCR1009.

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 23, 2015 10:20 pm
by czolo
We just have finished our third installation with Capsman, and we have some ideas:
1) Radius server should be cofigured for specific interface, like in hotspot, where I can chose a domain for a hotspot and than setup radius for a specific domain. In access-list it will be useful to have automated config for a specific authentication type. Now I have to choose interface from a list every time after update of the name. It can be more automarted
2) In registration all information should be visible like in normal mode (last-ip, routeros version etc.)
3) you should explain how regexp in names is working. MT gave us an option, bot nobody write an update to wiki. I want to see the interface with specific config with a specific name, now it's impossible. The same situation on CAP side - all interfaces have name wlan1,wlan2... - it should be the same name like in capsman.

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 23, 2015 10:30 pm
by avenn
Plus 1 for czolos suggestions

Re: CAPsMAN v2 ready for testing

Posted: Sun Jan 25, 2015 11:28 pm
by leoktv
I have been running 250 interfaces with caps-man and plus 800 clients online this was done with a ccr1009-8G-1S

Re: CAPsMAN v2 ready for testing

Posted: Mon Jan 26, 2015 11:31 am
by bartjoo
Hello,
Question1:
i want to auto provision with the auto provision tab. But it dont work :(
I connect the AP with the CAPsMan. That works. When i put the CFG in the CAP on tabblad INTERFACE, it works.
But when i go to tab Provisioning, and make a new rule, it dont work on the interfaces. :(

Someone could tell me why?
In the attachment my settings.

I tried, Create Dynamic enabled and Create enabled.
I tried also with the radio MAC (not 00:00:00:00:00:00).

---------------------
Question 2,
I have some AP's at restaurants. But they have a managed SSID (my SSID) and his own SSID for Local connections.
Is it possible to make with CAPsMan 1 managed and 1 unmanaged SSID. OR 2 managed but 1 of this is connected to the bridge on the clients side. ?


tnx for helping!

tnx for help.

Re: CAPsMAN v2 ready for testing

Posted: Mon Jan 26, 2015 1:50 pm
by bartjoo
Ah! The provisioning works! i had to delete the Interfaces.

now i will try the local forwarding.
i found this document.
http://file.accesspoint.hu/pdf/uldis.pdf
greetz

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 27, 2015 12:21 am
by SubOrbit
I have a RB751U-2HnD with ROS v6.25 and I cannot get CAP to connect to CAPsMAN, even if the capsman is on the same routerboard.
Identical configuration (without the 127.0.0.1 IP address) works like a charm on RB951G-2HnD. I would eventualy like the 751 to connect to the capsman on the 951, but since even a local connection doesnt work, I guess the problem in somewhere on the 751 board.

I have reset the board to defaults, set a local IP on the ether1 interface, added ether1 to bridge-local and disabled NAT, all firewall rules and DHCP server. Those are the only changes I have made from the default configuration.

I then enabled CAPsMan and CAP (see screenshot), but the connection is never established.

Any suggestions? Thanks!
751.jpg

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 27, 2015 10:22 am
by JasonEde
Having a serious issue with capsman v2. radios are rb912's running the current version 6.25(started with the first beta of v2). we have carts of hp stream 11 with realtek wireless cards, when more than ~10-15 connect to a single access point the throughput drops to almost nothing and the client begin to drop off. this happens without transferring data just connected. when i disable capsman and run the ap unmanaged the issue mostly goes away. the client chipset is rtl8723be, i know your going to say its the realtek but this does not happen on my meraki ap's(trying to get away from meraki)

The capsman controller is a ccr1009 and caps devices are running in local forwarding mode. it appears that the capsman is having an issue with the keeping up with the clients.
Did you manage to narrow down cause of your problem? We're about to roll out 912's for our radio on a 1100AHx2 capsman

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 27, 2015 10:50 am
by uldis
SubOrbit,
try to remote the CAPsMAN Name and Certificate common name and then check again if it establishes connection.
Also enable the caps,debug and wireless,debug logging so you would see the results of the CAPsMAN selection and some other debug logs.

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 27, 2015 12:49 pm
by SubOrbit
SubOrbit,
try to remote the CAPsMAN Name and Certificate common name and then check again if it establishes connection.
Also enable the caps,debug and wireless,debug logging so you would see the results of the CAPsMAN selection and some other debug logs.
I have removed capsman name and certificate common name and enabled caps,debug and wireless,debug. CAP discovery finds CAPsMAN, but after CAP Discover > Select, it says it did not find a suitable CAPsMAN (see screenshot)
751-2.jpg

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 27, 2015 2:44 pm
by SubOrbit
To answer my own question: my CAPsMAN names was wrong and when I removed the name, I did not disable the field (the capsman names field was still white), you have to disable the field (it has to be greyed out).

Everything is running smoothly now. Thanks!

Re: CAPsMAN v2 ready for testing

Posted: Wed Jan 28, 2015 8:39 am
by bartjoo
for me everything works now. local and forwarding.
another question, is it possible to use a variable for the SSID?
like: SSID: Test_[Identity] ?
Greetz
Bart

Re: CAPsMAN v2 ready for testing

Posted: Wed Jan 28, 2015 8:43 pm
by izytech
Is it possible to get information on which cap-interface a wireless client is connected to when using radius accounting? Perhaps in username field or in any other field if its possible. When using quite a lot of remote CAP it would be nice to collect som statistics over usage per remote cap.

Perhaps like this in username field

MACHW@CAPINTERFACENAME

Best regards,
Thomas

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 29, 2015 9:42 am
by bartjoo
Hello, another question. I made a FORWARDING bridge and it works fine.
But when i do a scan on this forwarding network, i found my apple tv airplay on the local network. How is this possible? This is a different network (or isnt?)
tnx for your help.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 29, 2015 1:34 pm
by uldis
if your cap interface in the full forwarding mode is in the bridge port with your local network then you will be in the same local network where you wireless clients are connected.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 29, 2015 1:39 pm
by bartjoo
I tried both.
with and without the local bridge. in both options airplay is there.

My config is:
AP1 - FULL Forwarding to datacenter (VPN), this is my hotspot (10.5.50.0/24)
AP2-virtual LOCAL FORWARDING with local bridge. (192.168.1.0/24) in the CAP MENU from the AP.

When i connect to AP1, i dont want to see thing on the local network. (like airplay).
When i connect to AP2, i want to see apple tv.

I tried also:
CAP MENU, disable local bridge. Only full forwarding. But i can activate Airplay also with AP1.

Do i need to work with VLAN?

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 29, 2015 3:18 pm
by uldis
AP1 and AP2 isn't in the same bridge? If not then you should not see the AP2 devices from the AP1.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 29, 2015 9:36 pm
by msport
Hi

Have been testing capsman, and it has some almost good enough features that we like, but is lacking in others:

We have a "big" network of 5Ghz AP's, all with their own ssid. Many stations use static ssid and as centralized CPE management is not possible, it is difficult to fix.

What I tought we would get with capsman, for starters:

Centralized management of radios. Feks, setting no ssid, cause all radios in group to use what is locally defined. (same principal on all settings basically)

Mac only authentication of clients (cpe's). Looks like capsman has this, but lack of features is not making it possible to use.

Centralized management of CPE related stuff. Signal, software upgrades etc.

Is this something that may happen sometime?

BR

Kim

Re: CAPsMAN v2 ready for testing

Posted: Thu Jan 29, 2015 11:00 pm
by bartjoo
if your cap interface in the full forwarding mode is in the bridge port with your local network then you will be in the same local network where you wireless clients are connected.
Hmm, i thought i know the problem. But its not. it dont work :(

connected with the hotspot, i found the 192.168 adresses with a scanner :(

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 30, 2015 11:53 am
by bartjoo
Hmm, i think i found something.
Even if i dont have a wifi connection, its possible to remote my apple tv.
so, its not a problem / question for capsman. sorry!

So, i will test capsman further. tnx for helping!

Re: CAPsMAN v2 ready for testing

Posted: Fri Jan 30, 2015 5:36 pm
by juanvi
Hi to all,

We have a all-in-one solution with radius(usermanager) for hotspot and wireless clients thanks to capsman. Features like CoA for wireless and EAP authentication using username/password for UserManager are missing but are in mikrotik's to-do list. With alternatives and some scripting we are doing the job almost fine.

We are very happy with capsman since we have 108 SSID's (54 radios) working as hotspot and wifi AP but there is a capsman feature i'm missing because clients can't connect in high density wi-fi zones. I'm aplying several methods for improving performance but there is a problem because we can not disble low wi-fi data rates. I can not disable only 802.11b too. Can't optimize the airtime utilization if we are allowing oldest modulations and 1Mbps data rates. Only option is allowing 802.11n ONLY and lower data rates are allowed anyway.

Can anyone tell me if this proposal would be effective ? Should be implemented ?

PD: We will use capsmanv1 until changes "test" to... at least "RC"!!! K'mon Mikrotik

Re: CAPsMAN v2 ready for testing

Posted: Mon Feb 02, 2015 4:30 pm
by JasonEde
We're finding that users keep getting disconnected (temporarily) and the throughput isn't that good (we've had 7Mbps x 2Mbps when we've a 100Mbps feed into our office). We're running capsman on an 1100AHx2 and the CAPs on RB912 (we've 2 of them). Everything is on RouterOS 6.23.

We've the access connection rules mentioned above to reject weak signal. The people getting disconnected are literally 3m-4m away from the access point.

Re: CAPsMAN v2 ready for testing

Posted: Mon Feb 02, 2015 4:50 pm
by uldis
Please upgrade to v6.25 with CAPsMAN v2 and check again.
Also check the wireless/caps debug logs for those disconnection reasons.

Re: CAPsMAN v2 ready for testing

Posted: Mon Feb 02, 2015 4:53 pm
by JasonEde
Will upgrade and try again. Where is the Capsman changelog? Doesn't look like it is part of the main changelog.

Re: CAPsMAN v2 ready for testing

Posted: Tue Feb 03, 2015 10:28 am
by JasonEde
All units are now running on 6.25 and I'm still seeing a lot of disconnects and moving between APs. Sample of the logs are below. All these devices are stationary in the building...

08:22:03 caps,info 74:E2:F5:22:12:67@AP2-Net1 connected
08:22:03 caps,info 74:E2:F5:22:12:67@AP1-Net1 disconnected, registered to other interface
08:22:07 caps,info 9C:04:EB:31:9B:BF@AP1-5GHz-Net2 connected
08:22:19 caps,info 9C:04:EB:31:9B:BF@AP1-5GHz-Net2 disconnected, too weak signal
08:23:23 caps,info F4:1B:A1:9A:19:0A@AP1-Net1 connected
08:23:29 caps,info F4:1B:A1:9A:19:0A@AP1-Net1 disconnected, 4-way handshake timeout
08:23:30 caps,info C8:85:50:6C:11:0B@AP1-Public-5G connected
08:23:30 caps,info C8:85:50:6C:11:0B@AP2-2.4GHz-Public disconnected, registered to other interface
08:23:31 caps,info C8:85:50:6C:11:0B@AP1-2.4GHz-Public connected
08:23:31 caps,info C8:85:50:6C:11:0B@AP1-Public-5G disconnected, registered to other interface
08:23:37 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 connected
08:23:40 caps,info B8:E8:56:76:05:C3@AP2-5GHz-Net2 connected
08:23:40 caps,info B8:E8:56:76:05:C3@AP1-5GHz-Net2 disconnected, registered to other interface
08:23:43 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 disconnected, too weak signal
08:23:46 caps,info B8:E8:56:76:05:C3@AP2-5GHz-Net2 disconnected, too weak signal
08:23:48 caps,info B8:E8:56:76:05:C3@AP1-5GHz-Net2 connected
08:23:50 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 connected
08:23:54 caps,info C8:85:50:6C:11:0B@AP1-2.4GHz-Public disconnected, extensive data loss
08:23:56 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 disconnected, too weak signal
08:24:05 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 connected
08:24:08 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 disconnected, too weak signal

Re: CAPsMAN v2 ready for testing

Posted: Fri Feb 06, 2015 4:24 pm
by czolo
I have a question, why I can't configure vlan-mode on virtual-ap?

I can set it in normal mode only for master wlan card. If I'm using capsman, I can put a traffic from specific slave vap into a vlan. So why this funcionality is not accesible in normal mode for manualy created vap?

Re: CAPsMAN v2 ready for testing

Posted: Sat Feb 14, 2015 9:27 am
by sguox
is there any plan to support station bridge?

Re: CAPsMAN v2 ready for testing

Posted: Mon Feb 16, 2015 10:23 am
by JanezFord
2) In registration all information should be visible like in normal mode (last-ip, routeros version etc.)
+1 for Last-IP
I would also like to see RT/TX CCQ and signal-to-noise.

Anyone knows how to set WMM, HW Protection Mode, Preamble Mode, HW Retries and other advanced mode parameters with CAPsMAN v2 ? If it is not yet possible does anyone know if there are any plans to add these configuration options to CAPsMAN v2 in the future?

JF.

Re: CAPsMAN v2 ready for testing

Posted: Thu Feb 19, 2015 8:27 am
by Zwodka
I plan to by a RB911G-2HPnD and a RB911G-5HPnD for AP. But they have Licence Level 3 : no Wireless AP permitted :-(
But what about in CAPsMAN configuration?
I mean:
- one Licence Level 4/5/6 RB as CAPsMAN,
and
- RB911G-2HPnD/-5HPnD serie as CAP device.

Re: CAPsMAN v2 ready for testing

Posted: Thu Feb 19, 2015 10:12 am
by juanvi
I plan to by a RB911G-2HPnD and a RB911G-5HPnD for AP. But they have Licence Level 3 : no Wireless AP permitted :-(
But what about in CAPsMAN configuration?
I mean:
- one Licence Level 4/5/6 RB as CAPsMAN,
and
- RB911G-2HPnD/-5HPnD serie as CAP device.
I'm not sure but i think is the same for CAPSMAN. At the end you have one ap and is remotelly controlled.
I think you need L4 license to have more tan one client in local or CAP (ptp link is allowed with L3 license).

I've buyed 2 SXT Lite2 and are L3. They say: "SXT Lite2 is a low cost, high transmit power 2.4GHz (2312 -2732MHz depending on country regulations) outdoor wireless device. It can be used for point to point links or as a CPE for point to multipoint installations"

Anyway not tried yet but i've readed ptp is posible with L3 and bridge/station bridge mode.

I'm not 100% sure. Only logic answer.

Re: CAPsMAN v2 ready for testing

Posted: Thu Feb 19, 2015 7:30 pm
by uldis
you need RouterOS Level 4 licenese to make a board as a CAP AP.
Level 3 license is only for point-to-point pinks.

Station-bridge mode is not supported with CAPsMAN at the moment.

Re: CAPsMAN v2 ready for testing

Posted: Fri Feb 20, 2015 8:13 am
by Zwodka
Thanx for the answer!

Re: CAPsMAN v2 ready for testing

Posted: Fri Feb 20, 2015 10:45 am
by juanvi
I plan to by a RB911G-2HPnD and a RB911G-5HPnD for AP. But they have Licence Level 3 : no Wireless AP permitted :-(
But what about in CAPsMAN configuration?
I mean:
- one Licence Level 4/5/6 RB as CAPsMAN,
and
- RB911G-2HPnD/-5HPnD serie as CAP device.
I'm not sure but i think is the same for CAPSMAN. At the end you have one ap and is remotelly controlled.
I think you need L4 license to have more tan one client in local or CAP (ptp link is allowed with L3 license).

I've buyed 2 SXT Lite2 and are L3. They say: "SXT Lite2 is a low cost, high transmit power 2.4GHz (2312 -2732MHz depending on country regulations) outdoor wireless device. It can be used for point to point links or as a CPE for point to multipoint installations"

Anyway not tried yet but i've readed ptp is posible with L3 and bridge/station bridge mode.

I'm not 100% sure. Only logic answer.
Uldis said: "you need RouterOS Level 4 licenese to make a board as a CAP AP.
Level 3 license is only for point-to-point pinks."

I do not understand why an L3 AP with one client (ptp) is possible and the same, but remotelly controlled, is not possible.
Can you explain please?

Uldis said: "Station-bridge mode is not supported with CAPsMAN at the moment."
CAP=Controlled Access Point
CAPsMAN= Manager for Controlled Access Points
Looking for "Controlled STATION" ??? CSTA??? And his manager... CSTAsMAN...
What sense has this???

Today do not understand anything. ;-)

Re: CAPsMAN v2 ready for testing

Posted: Fri Feb 20, 2015 1:06 pm
by uldis
Currently CAPsMAN is not designed for management of the WISP APs as it doesn't support Bridge mode that is required for Station-Bridge and WDS that is required for the Station-WDS.
We might add those features later when we have finished the rest of the CAPsMAN planned features.

Re: CAPsMAN v2 ready for testing

Posted: Wed Feb 25, 2015 6:39 pm
by juanvi
Currently CAPsMAN is not designed for management of the WISP APs as it doesn't support Bridge mode that is required for Station-Bridge and WDS that is required for the Station-WDS.
We might add those features later when we have finished the rest of the CAPsMAN planned features.
Ok. I understand you now but, this is an option for a inadvisable full bridged network. Broadcast domain becomes huge and have their pants down for a broadcast storm. Best route at CPE and isolate your network from client's broadcast. Ap mode under CAPsMAN would be advisable. I'm right?

Re: CAPsMAN v2 ready for testing

Posted: Fri Feb 27, 2015 9:43 am
by bartjoo
Currently CAPsMAN is not designed for management of the WISP APs as it doesn't support Bridge mode that is required for Station-Bridge and WDS that is required for the Station-WDS.
We might add those features later when we have finished the rest of the CAPsMAN planned features.
Hello, Is there a list available with the (roadmap) new features?

Re: CAPsMAN v2 ready for testing

Posted: Tue Mar 03, 2015 9:26 pm
by hngjared
I'm just starting to demo the CAPsMANv2.

When I remove the CAPsMAN from the network for a few seconds and reconnect my APs(CAPS) do not reconnect unless I reboot or disable/re-enable the CAP in the wireless interface of the AP.

Is this normal? Is there a setting I'm missing that allows the units to sync back together after a brief interruption?

I appreciate any feed back.

Re: CAPsMAN v2 ready for testing

Posted: Tue Mar 03, 2015 9:28 pm
by bartjoo
I'm just starting to demo the CAPsMANv2.

When I remove the CAPsMAN from the network for a few seconds and reconnect my APs(CAPS) do not reconnect unless I reboot or disable/re-enable the CAP in the wireless interface of the AP.

Is this normal? Is there a setting I'm missing that allows the units to sync back together after a brief interruption?

I appreciate any feed back.
No, this is not correct. When he gets a connection with CAPsMAN again, he will send the WiFi signal again.

Re: CAPsMAN v2 ready for testing

Posted: Tue Mar 03, 2015 9:48 pm
by hngjared
I appreciate the quick response.

My problem is I unhooked the CAPsMAN controller from the LAN for about 30 seconds and plugged it back up. Once plugged back in the access points never sync back with the controller? You'd think this would happen quickly and automatically. But, I'm unable to get the units to SYNC back with the controller unless I reboot or disable/re-enable the CAP on the AP.

Worst case scenario. My controller drops offline for 5 minutes. Would I be required to go around and reboot 200 APs to regain sync to the controller? Do I need to implement a script to disable/re-enable the CAP. How do other people get their equipment to regain access to the controller?

Thanks!

Re: CAPsMAN v2 ready for testing

Posted: Tue Mar 03, 2015 9:51 pm
by bartjoo
I appreciate the quick response.

My problem is I unhooked the CAPsMAN controller from the LAN for about 30 seconds and plugged it back up. Once plugged back in the access points never sync back with the controller? You'd think this would happen quickly and automatically. But, I'm unable to get the units to SYNC back with the controller unless I reboot or disable/re-enable the CAP on the AP.

Worst case scenario. My controller drops offline for 5 minutes. Would I be required to go around and reboot 200 APs to regain sync to the controller? Do I need to implement a script to disable/re-enable the CAP. How do other people get their equipment to regain access to the controller?

Thanks!
could you tell more about your infrastructure and mikrotik OS / Capsman version?

Re: CAPsMAN v2 ready for testing

Posted: Tue Mar 03, 2015 9:58 pm
by hngjared
I'm working in a testing environment with a very basic layout.

I'm using the latest version of Router OS and CAPsMANv2 on 6.27.

I have a 5 port RB450G gateway connected to a 5 port 750UP POE switch powering 4 RB912UAG-2HPnD APs. I have the 450G acting as the controller for the 4 APs.

Everything works fine until the AP loses connection to the controller for as little as a few seconds. After that the AP never re-establishes a connection back to the controller.

Thanks!

Re: CAPsMAN v2 ready for testing

Posted: Fri Mar 06, 2015 9:52 am
by bartjoo
I'm working in a testing environment with a very basic layout.

I'm using the latest version of Router OS and CAPsMANv2 on 6.27.

I have a 5 port RB450G gateway connected to a 5 port 750UP POE switch powering 4 RB912UAG-2HPnD APs. I have the 450G acting as the controller for the 4 APs.

Everything works fine until the AP loses connection to the controller for as little as a few seconds. After that the AP never re-establishes a connection back to the controller.

Thanks!
Hmm, could you upload a image of your settings for CAPsman?
or your settings file from your main and client routeR?

Re: CAPsMAN v2 ready for testing

Posted: Fri Mar 06, 2015 11:00 am
by uldis
are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?

Re: CAPsMAN v2 ready for testing

Posted: Fri Mar 06, 2015 4:21 pm
by hngjared
are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?
Using wireless-cm2 package and connected via MAC.

Very basic created Config and applied to the CAP when it showed up in the interfaces.

Again, everything works fine until the CAP disconnects from the controller. There after it will not reconnect until the CAP is disabled/re-enabled or the AP is power cycled.

Thanks!

Re: CAPsMAN v2 ready for testing

Posted: Fri Mar 06, 2015 4:22 pm
by bartjoo
are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?
Using wireless-cm2 package and connected via MAC.

Very basic created Config and applied to the CAP when it showed up in the interfaces.

Again, everything works fine until the CAP disconnects from the controller. There after it will not reconnect until the CAP is disabled/re-enabled or the AP is power cycled.

Thanks!
could you try it with IP addresses? I work with IP's and it works fine.

Re: CAPsMAN v2 ready for testing

Posted: Fri Mar 06, 2015 5:13 pm
by hngjared
are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?
Using wireless-cm2 package and connected via MAC.

Very basic created Config and applied to the CAP when it showed up in the interfaces.

Again, everything works fine until the CAP disconnects from the controller. There after it will not reconnect until the CAP is disabled/re-enabled or the AP is power cycled.

Thanks!
could you try it with IP addresses? I work with IP's and it works fine.
I tested for a bit longer. I originally tested with only the CAPsMAN Address (IP) configured in the CAP. Once I added the CAPsMAN Name everything started syncing immediately after reconnecting to the network.

Not sure why the IP address wasn't working but we'll take it.

Re: CAPsMAN v2 ready for testing

Posted: Mon Mar 23, 2015 6:28 pm
by Namaveedu
I Agree,, This is useful information Thanks..

Re: CAPsMAN v2 ready for testing

Posted: Sat Mar 28, 2015 7:22 pm
by chechito
CAPsMAN is mostly meant for managing of access points in hotels, homes, apartments, offices etc. the clients in these places are windows and mac laptops, phones etc. 
I thing, you need more work about fast roaming in capsman 2

Wifi device need to lost of signal on cap1 to connect another cap2, but wifi device can work long time with cap1 on signal -89 even the cap2 is closer with signal -40

bleblas
one solution is manipulating datarates, disabling slower datarates client jump to another AP before reaching such lower signal level.

but capsman not allow manipulating datarates, its the main reason because i dont use capsman

Re: CAPsMAN v2 ready for testing

Posted: Tue Mar 31, 2015 4:40 am
by chechito
All units are now running on 6.25 and I'm still seeing a lot of disconnects and moving between APs. Sample of the logs are below. All these devices are stationary in the building...

08:22:03 caps,info 74:E2:F5:22:12:67@AP2-Net1 connected
08:22:03 caps,info 74:E2:F5:22:12:67@AP1-Net1 disconnected, registered to other interface
08:22:07 caps,info 9C:04:EB:31:9B:BF@AP1-5GHz-Net2 connected
08:22:19 caps,info 9C:04:EB:31:9B:BF@AP1-5GHz-Net2 disconnected, too weak signal
08:23:23 caps,info F4:1B:A1:9A:19:0A@AP1-Net1 connected
08:23:29 caps,info F4:1B:A1:9A:19:0A@AP1-Net1 disconnected, 4-way handshake timeout
08:23:30 caps,info C8:85:50:6C:11:0B@AP1-Public-5G connected
08:23:30 caps,info C8:85:50:6C:11:0B@AP2-2.4GHz-Public disconnected, registered to other interface
08:23:31 caps,info C8:85:50:6C:11:0B@AP1-2.4GHz-Public connected
08:23:31 caps,info C8:85:50:6C:11:0B@AP1-Public-5G disconnected, registered to other interface
08:23:37 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 connected
08:23:40 caps,info B8:E8:56:76:05:C3@AP2-5GHz-Net2 connected
08:23:40 caps,info B8:E8:56:76:05:C3@AP1-5GHz-Net2 disconnected, registered to other interface
08:23:43 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 disconnected, too weak signal
08:23:46 caps,info B8:E8:56:76:05:C3@AP2-5GHz-Net2 disconnected, too weak signal
08:23:48 caps,info B8:E8:56:76:05:C3@AP1-5GHz-Net2 connected
08:23:50 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 connected
08:23:54 caps,info C8:85:50:6C:11:0B@AP1-2.4GHz-Public disconnected, extensive data loss
08:23:56 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 disconnected, too weak signal
08:24:05 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 connected
08:24:08 caps,info 80:E6:50:11:A2:26@AP1-5GHz-Net2 disconnected, too weak signal
i note the same result using acl to disconnect weak signal clients, i think client signal strength fluctuate a lot and generates false positives on the acl.

I encountered disabling lower datarates a more effective strategy to disconnect weak signal clientes before they degradate performance of the AP, its the main reason i dont use CAPSMAN, because CAPSMAN NOT SUPPORTS DISABLING DATARATES ON RADIOS :( :( :(

Re: CAPsMAN v2 ready for testing

Posted: Thu Apr 02, 2015 1:04 am
by chechito
testing package on rb951g

without connecting to CAPSMAN

slower wifi performance and random disconnects

ros 6.27, firmware 3.22

rolling back to wireless-fp :?

Re: CAPsMAN v2 ready for testing

Posted: Thu Apr 02, 2015 7:31 pm
by uldis
testing package on rb951g

without connecting to CAPSMAN

slower wifi performance and random disconnects

ros 6.27, firmware 3.22

rolling back to wireless-fp :?
Please contact support@mikrotik.com about this problem and also tell us how you are measuring the performance.

Re: CAPsMAN v2 ready for testing

Posted: Thu Apr 16, 2015 7:17 pm
by popovdv
Please add feature to CapsMan controller to see what frequency using remote CAP

Re: CAPsMAN v2 ready for testing

Posted: Fri Apr 17, 2015 6:32 pm
by avenn
Hello,

Feature update please:

When will scanlist and registration table with frame + hw-frame details be implemented in CAPsMANv2.

We need to be able to adpat more to layer 1 and monitor layer 2 as you can when AP standalone.

The lack of these features is a signiifacnt regression especially for a large scale implementation.

Regards

Aidan

Re: CAPsMAN v2 ready for testing

Posted: Sat Apr 18, 2015 9:42 am
by JasonEde
On 6.27 (ppc on 1100AHx2) with CM2 enabled if I try and get the OID list for snmp monitoring I can see...

/caps-man registration-table> print oid
0 ;;; Accept connections if signal stronger than -80
mac-address=.1.3.6.1.4.1.14988.1.1.1.4.1.1.16.104.63.132.124.142.85
uptime=.1.3.6.1.4.1.14988.1.1.1.4.1.3.16.104.63.132.124.142.85
tx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.4.16.104.63.132.124.142.85
rx-bytes=.1.3.6.1.4.1.14988.1.1.1.4.1.5.16.104.63.132.124.142.85
tx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.6.16.104.63.132.124.142.85
rx-packets=.1.3.6.1.4.1.14988.1.1.1.4.1.7.16.104.63.132.124.142.85
tx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.8.16.104.63.132.124.142.85
rx-rate=.1.3.6.1.4.1.14988.1.1.1.4.1.9.16.104.63.132.124.142.85
tx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.10.16.104.63.132.124.142.85
rx-signal=.1.3.6.1.4.1.14988.1.1.1.4.1.11.16.104.63.132.124.142.85

However, a snmpwalk or snmpget for these yields nothing... Does this work for anyone?

Edited to add... I've just managed to browse this..

iso.3.6.1.4.1.14988.1.1.1.5.1.1.16.104.63.132.124.142.85 = Hex-STRING: 10 68 3F 84 7C 8E
iso.3.6.1.4.1.14988.1.1.1.5.1.3.16.104.63.132.124.142.85 = Timeticks: (7145200) 19:50:52.00
iso.3.6.1.4.1.14988.1.1.1.5.1.4.16.104.63.132.124.142.85 = Counter32: 5326
iso.3.6.1.4.1.14988.1.1.1.5.1.5.16.104.63.132.124.142.85 = Counter32: 7354
iso.3.6.1.4.1.14988.1.1.1.5.1.6.16.104.63.132.124.142.85 = Counter32: 51
iso.3.6.1.4.1.14988.1.1.1.5.1.7.16.104.63.132.124.142.85 = Counter32: 59
iso.3.6.1.4.1.14988.1.1.1.5.1.8.16.104.63.132.124.142.85 = Gauge32: 13000000
iso.3.6.1.4.1.14988.1.1.1.5.1.9.16.104.63.132.124.142.85 = Gauge32: 58500000
iso.3.6.1.4.1.14988.1.1.1.5.1.10.16.104.63.132.124.142.85 = INTEGER: 0
iso.3.6.1.4.1.14988.1.1.1.5.1.11.16.104.63.132.124.142.85 = INTEGER: -59

This looks like the data I'm looking for, but is on 1.1.1.5 not .4 as reported above. Is that a mistake in what is reported when you do print oid?

Re: CAPsMAN v2 ready for testing

Posted: Mon Apr 27, 2015 6:48 pm
by ivicav
I set one pair of RB 951G-2HnD in production but I have a bunch of issues here. Here is my log:
17:38:57 caps,info 84:63:D6:98:85:0C@cap3 disconnected, extensive data loss 
17:38:58 caps,info 00:BB:3A:F6:70:02@cap6 disconnected, 4-way handshake timeout 
17:39:06 caps,info 00:BB:3A:F6:70:02@cap6 connected 
17:39:12 caps,info 00:BB:3A:F6:70:02@cap6 disconnected, 4-way handshake timeout 
17:39:12 caps,info 00:BB:3A:F6:70:02@cap2 connected 
17:39:16 caps,info 00:BB:3A:F6:70:02@cap2 disconnected, received disassoc: sending station leaving (8) 
17:39:20 caps,info 00:BB:3A:F6:70:02@cap6 connected 
17:39:26 caps,info 00:BB:3A:F6:70:02@cap6 disconnected, 4-way handshake timeout 
17:39:26 caps,info 00:BB:3A:F6:70:02@cap2 connected 
17:39:30 caps,info 00:BB:3A:F6:70:02@cap2 disconnected, received disassoc: sending station leaving (8) 
17:39:34 caps,info 00:EE:BD:AB:4D:93@cap5 connected 
17:39:35 caps,info 00:EE:BD:AB:4D:93@cap3 disconnected, registered to other interface 
17:39:35 caps,info 00:BB:3A:F6:70:02@cap6 connected 
17:39:41 caps,info 00:BB:3A:F6:70:02@cap6 disconnected, 4-way handshake timeout 
17:39:41 caps,info 00:BB:3A:F6:70:02@cap2 connected 
17:39:47 caps,info 00:BB:3A:F6:70:02@cap2 disconnected, 4-way handshake timeout 
17:40:03 caps,info CC:89:FD:A8:90:CC@cap6 connected 
17:40:09 caps,info CC:89:FD:A8:90:CC@cap6 disconnected, received disassoc: unspecified (1) 
17:40:13 caps,info CC:89:FD:A8:90:CC@cap5 connected 
17:40:18 caps,info CC:89:FD:A8:90:CC@cap5 disconnected, received disassoc: unspecified (1) 
17:42:09 caps,info CC:89:FD:A8:90:CC@cap6 connected 
17:42:14 caps,info CC:89:FD:A8:90:CC@cap6 disconnected, received disassoc: unspecified (1) 
17:42:19 caps,info CC:89:FD:A8:90:CC@cap5 connected 
17:42:23 caps,info E8:99:C4:B7:15:5E@cap2 disconnected, received disassoc: sending station leaving (8) 
17:42:24 caps,info CC:89:FD:A8:90:CC@cap5 disconnected, received disassoc: unspecified (1) 
17:44:15 caps,info CC:89:FD:A8:90:CC@cap6 connected 
17:44:20 caps,info CC:89:FD:A8:90:CC@cap6 disconnected, received disassoc: unspecified (1) 
17:44:25 caps,info CC:89:FD:A8:90:CC@cap5 connected 
17:44:30 caps,info CC:89:FD:A8:90:CC@cap5 disconnected, received disassoc: unspecified (1) 
As you can see there is lot of drop outs. Clients keep disconnected sometimes after few minutes, sometime after few seconds... And some of clients are OK.

Re: CAPsMAN v2 ready for testing

Posted: Tue May 05, 2015 5:29 am
by telipcomx
Hi I was used capsman v1 with rb1100 and arround 40 hotspots with rbmetal or groove, my expience is bad all y clients have a problems with "radius server not responding" or "username or password not found" and the clasic "your account is use now" , this version have solution for this problems

thanks

Re: CAPsMAN v2 ready for testing

Posted: Thu May 07, 2015 4:57 pm
by hengst
Any news about :

- live auto frequency selection per AP ( based on live Spectrum , without having enable/disable interface )
- auto Tx-power control ( based on own neighbour Ap's )

or is this already build in at the moment ?

Re: CAPsMAN v2 ready for testing

Posted: Fri May 08, 2015 1:14 pm
by avenn
Any news about :

- live auto frequency selection per AP ( based on live Spectrum , without having enable/disable interface )
- auto Tx-power control ( based on own neighbour Ap's )

or is this already build in at the moment ?

+100000

Re: CAPsMAN v2 ready for testing

Posted: Fri May 08, 2015 6:52 pm
by chechito
Any news about :

- live auto frequency selection per AP ( based on live Spectrum , without having enable/disable interface )
- auto Tx-power control ( based on own neighbour Ap's )

or is this already build in at the moment ?
ok lets take other brands marketing to the reality:

to do that you request its necessary a second radio on the ap for the only purpose or spectrum analysis and neighbor monitoring.

Automatic spectrum analysis requires a development beyond the actual scope of ROS.

Some people like all in life to be automatic but it has associated costs.

i will be happy with datarates and ht mcs manageable from CAPsMAN its the only thing prevents me from using CAPsMAN

Re: CAPsMAN v2 ready for testing

Posted: Mon May 11, 2015 1:02 pm
by hengst
o do that you request its necessary a second radio on the ap for the only purpose or spectrum analysis and neighbor monitoring.

Automatic spectrum analysis requires a development beyond the actual scope of ROS.

Some people like all in life to be automatic but it has associated costs.

i will be happy with datarates and ht mcs manageable from CAPsMAN its the only thing prevents me from using CAPsMAN
maybe better id is to let the Ap create its own little statistics database in some time about freq / neighbours / CCQ etc. and let the Ap make a decision of what settings to use based on statistical information over some time.

In time it would tune itself to the best setting available on the location if set to "auto config". or for those how like to be in control, let capsman notify you the Ap probably could perform better on channel X with setting X , and you could click a provision button to make it real.

Re: CAPsMAN v2 ready for testing

Posted: Sat May 16, 2015 11:28 am
by NetworkMeister
I have constant problems with certificates when running CAPsMAN and CAP on the same router. Whenever I do a fresh configuration, issue new CA & certificates and join local CAP to CAPsMAN on the same router, things work fine. However, after reboot of the router, I am starting to get certificate errors. Apparently CAP is trying to locally install Certificates it gets from CAPsMAN, but fails to do so, since the certificates are already installed (well, it's the same router!). This process keeps repeating for about 2 days, until router runs ouf of memory and reboots :) I have no problems with CAPs that connect from other routers.

I have set local CAP configuration to Certificate: none, but the issue remains.

Any idea?
Capture.PNG
Capture2.PNG

Re: CAPsMAN v2 ready for testing

Posted: Mon May 18, 2015 9:27 pm
by wombat
Hi!

Where can I get package of CAPsMan v2 for 6.29 (RC20)? in all_files is not there..

Thank you.

Re: CAPsMAN v2 ready for testing

Posted: Tue May 19, 2015 10:20 am
by karlisi
Hi!

Where can I get package of CAPsMan v2 for 6.29 (RC20)? in all_files is not there..

Thank you.
http://www.mikrotik.com/download/share/ ... mipsbe.npk

Change "mispbe" with you router architecture.

Re: CAPsMAN v2 ready for testing

Posted: Wed Jun 10, 2015 9:20 pm
by solaoxo
When CAPsMAN v2 switch latency, no better than the switched wds, wds truly seamless switching.

Re: CAPsMAN v2 ready for testing

Posted: Mon Jun 22, 2015 1:37 pm
by Cornmeister
When I take a look at the logs, I see a lot of MAC addresses for all connecting clients.
is it possible to enter a description for these addresses to identify them ?

something like
12:08:15 caps,info IPhone6_A@AP_Switchruimte connected
12:08:21 caps,info IPhone6_A@AP_Woonkamer_Pa_en_Ma connected
12:08:21 caps,info IPhone6_A@AP_Switchruimte disconnected, registered to other interface
12:13:05 caps,info Samsung_Tab@AP_Switchruimte connected
12:26:38 caps,info Laptop@AP_Switchruimte connected
12:26:38 caps,info Laptop@AP_Woonkamer_Pa_en_Ma disconnected, registered to other interface
12:32:10 caps,info Laptop@AP_Woonkamer_Pa_en_Ma connected
12:32:10 caps,info Laptop@AP_Switchruimte disconnected, registered to other interface
instead of
12:08:15 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte connected
12:08:21 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma connected
12:08:21 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte disconnected, registered to other interface
12:13:05 caps,info D4:F4:6F:9B:EB:9A@AP_Switchruimte connected
12:26:38 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte connected
12:26:38 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma disconnected, registered to other interface
12:32:10 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma connected
12:32:10 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte disconnected, registered to other interface

Re: CAPsMAN v2 ready for testing

Posted: Sat Jun 27, 2015 3:58 pm
by Beone
For mobile wireless device compatibility reasons (the wireless goes on/off everytime they go into standby) i need to change the WPA2 group-key timeout to something higher; to something like an hour as example

It seems it is currently not possible to set the group-key timeout in capsmanv2? (tested up to V6.30rc22)

Is this functionality planned to be added? (it is required to avoid continuous disconnects for mobile clients)

Re: CAPsMAN v2 ready for testing

Posted: Mon Jun 29, 2015 10:22 am
by juanvi
Why cannot v1 CAPs connect to v2 CAPsMAN or vice-versa? Aren't CAPsMAN v1 and v2 both RFC5416 (CAPWAP) compliant?

-- Nathan
Answered in post 13 of the first page of this thread:
"CAPsMAN v2 is not capwap compliant due to limitations of capwap protocol"

Re: CAPsMAN v2 ready for testing

Posted: Mon Jun 29, 2015 10:29 am
by juanvi
Very interesting, could someone share info about how this "improved logging entries when client roams between the CAPs"

Info like: "MAC XX:XX:XX:XX:XX:XX on CAP X disconnected, registered to other interface" will be displayed. This question was already answered in the 8th post of this thread. You can read all first if you have more questions.

Re: CAPsMAN v2 ready for testing

Posted: Wed Jul 01, 2015 12:11 pm
by Zwodka
Hi All,

I use CAPsMAN and it works "fine". But when I change Cap-Interface -> Channel -> Band to "2ghz-onlyn" the interface shows me:
- managed by CAPsMAN
- channel 2432/20/gn(20dBm)
gn? Why?

Re: CAPsMAN v2 ready for testing

Posted: Wed Jul 01, 2015 12:42 pm
by uldis
It shows GN because that only-n mode only changes the basic-rates setting, G mode data-rates are still used. Here is the table with the explanation for each mode:
http://wiki.mikrotik.com/wiki/Manual:In ... Rate_table

Re: CAPsMAN v2 ready for testing

Posted: Wed Jul 01, 2015 5:57 pm
by Zwodka
It shows GN because that only-n mode only changes the basic-rates setting, G mode data-rates are still used. Here is the table with the explanation for each mode:
http://wiki.mikrotik.com/wiki/Manual:In ... Rate_table
MegaThanx

Re: CAPsMAN v2 ready for testing

Posted: Wed Jul 01, 2015 6:35 pm
by panosla
Is DHCP option 138 suitable for configuring CAPsMAN address on all CAP enabled devices?

Re: CAPsMAN v2 ready for testing

Posted: Thu Jul 02, 2015 12:45 pm
by uldis
Yes.

Configuring DHCP Server Option 138 for setting the CAPsMAN address on the CAP boards:

/ip dhcp-server network set <network-id> caps-manager=<capsman-server-ip>

DHCP client this CAPsMAN IP will see in "/ip dhcp-client print detail"

Re: CAPsMAN v2 ready for testing

Posted: Mon Jul 06, 2015 7:12 pm
by solaoxo
Just across the middle CAPsMAN other brands would not recognize the switch.

Re: CAPsMAN v2 ready for testing

Posted: Wed Jul 15, 2015 5:13 pm
by P2k1
where do I find cm2 package for 6.30 6.30.1?
didn't find it on the download page.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jul 16, 2015 8:20 am
by karlisi
where do I find cm2 package for 6.30 6.30.1?
didn't find it on the download page.
Starting from 6.30 it's included in main package.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jul 16, 2015 9:20 am
by P2k1
where do I find cm2 package for 6.30 6.30.1?
didn't find it on the download page.
Starting from 6.30 it's included in main package.
Thanks, so i'm going to update. :)

Re: CAPsMAN v2 ready for testing

Posted: Thu Jul 16, 2015 11:30 am
by karlisi
After successfull update there will be cm2 package file in /files, AFAIK it is for compatibility purposes, you can delete it, otherwise you will receive error "package already installed" on every reboot.

Re: CAPsMAN v2 ready for testing

Posted: Thu Jul 30, 2015 5:04 pm
by bartjoo
Hello,
could you tell what the new features are for the next version (v3)?
And could you tell when v3 is planned?

Re: CAPsMAN v2 ready for testing

Posted: Tue Aug 04, 2015 1:41 am
by MikroTicked
I have constant problems with certificates when running CAPsMAN and CAP on the same router. Whenever I do a fresh configuration, issue new CA & certificates and join local CAP to CAPsMAN on the same router, things work fine. However, after reboot of the router, I am starting to get certificate errors. Apparently CAP is trying to locally install Certificates it gets from CAPsMAN, but fails to do so, since the certificates are already installed (well, it's the same router!). This process keeps repeating for about 2 days, until router runs ouf of memory and reboots :) I have no problems with CAPs that connect from other routers.

I have set local CAP configuration to Certificate: none, but the issue remains.

Any idea?
Was this issue resolved? I'm having exactly the same problem.

Re: CAPsMAN v2 ready for testing

Posted: Tue Aug 04, 2015 10:54 am
by Cornmeister
*bump*
When I take a look at the logs, I see a lot of MAC addresses for all connecting clients.
is it possible to enter a description for these addresses to identify them ?

something like
12:08:15 caps,info IPhone6_A@AP_Switchruimte connected
12:08:21 caps,info IPhone6_A@AP_Woonkamer_Pa_en_Ma connected
12:08:21 caps,info IPhone6_A@AP_Switchruimte disconnected, registered to other interface
12:13:05 caps,info Samsung_Tab@AP_Switchruimte connected
12:26:38 caps,info Laptop@AP_Switchruimte connected
12:26:38 caps,info Laptop@AP_Woonkamer_Pa_en_Ma disconnected, registered to other interface
12:32:10 caps,info Laptop@AP_Woonkamer_Pa_en_Ma connected
12:32:10 caps,info Laptop@AP_Switchruimte disconnected, registered to other interface
instead of
12:08:15 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte connected
12:08:21 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma connected
12:08:21 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte disconnected, registered to other interface
12:13:05 caps,info D4:F4:6F:9B:EB:9A@AP_Switchruimte connected
12:26:38 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte connected
12:26:38 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma disconnected, registered to other interface
12:32:10 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma connected
12:32:10 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte disconnected, registered to other interface

Re: CAPsMAN v2 ready for testing

Posted: Tue Aug 04, 2015 3:26 pm
by Beone
We are massively deploying CAPSMANv2 now but are suffering controller cpu spikes to 100%.

We have a Mikrotik case open (started at V6.29.1 and are now running V6.30.2 but still having the issues) but wanted some feedback of people maybe running into the same issues?

- process ssl @100% cpu when caps try to connect with connection errors (timeouts)
- process wireless suddenly hangs for hours @ 100% cpu after 9-10hours running resulting in caps not failing over to backup controller and just dropping the complete wireless network

The controller is not performing any forwarding of the traffic, it merely manages all the caps and their configuration.

We tried RB450G as controller; then moved on to RB850Gx2 (which is a bit better) but still no luck.

I've read people in the forum here running it on CCR1009 in hotels with no issues. Can they confirm that the ssl and wireless processes are multi-thread capable and can be offloaded to multiple CCR cores?

There currently doesn't seem to be a performance indicator yet on CAPSMAN controller sizing

Re: CAPsMAN v2 ready for testing

Posted: Wed Aug 05, 2015 12:44 am
by MikroTicked
I have constant problems with certificates when running CAPsMAN and CAP on the same router. Whenever I do a fresh configuration, issue new CA & certificates and join local CAP to CAPsMAN on the same router, things work fine. However, after reboot of the router, I am starting to get certificate errors. Apparently CAP is trying to locally install Certificates it gets from CAPsMAN, but fails to do so, since the certificates are already installed (well, it's the same router!). This process keeps repeating for about 2 days, until router runs ouf of memory and reboots :) I have no problems with CAPs that connect from other routers.

I have set local CAP configuration to Certificate: none, but the issue remains.

Any idea?
Was this issue resolved? I'm having exactly the same problem.
It seems that the problem is related to the CAP not being able to load the certificate that was created when it first registered with the CAPsMAN (on the same device). When I select the issued certificate in the dialog box to enable CAP, the log shows "CAP connect to Router (xxxxx) failed: could not load certificate (6)"

Device 951G-2HnD
OS 6.30.2
Firmware 3.24

Re: CAPsMAN v2 ready for testing

Posted: Wed Aug 05, 2015 8:12 am
by karlisi
We are running CAPsMAN v2 controllers on CCR1009 with no problems. Also have one on RB1100 (1 CPU), works OK. One difference, our controllers are traffic forwarders too.

Re: CAPsMAN v2 ready for testing

Posted: Wed Aug 12, 2015 11:44 am
by Zwodka
Is there any way to change HT-MCS settings under CAPsMAN?

Re: CAPsMAN v2 ready for testing

Posted: Sat Aug 15, 2015 11:52 am
by Tr0llk1ng
I have constant problems with certificates when running CAPsMAN and CAP on the same router. Whenever I do a fresh configuration, issue new CA & certificates and join local CAP to CAPsMAN on the same router, things work fine. However, after reboot of the router, I am starting to get certificate errors. Apparently CAP is trying to locally install Certificates it gets from CAPsMAN, but fails to do so, since the certificates are already installed (well, it's the same router!). This process keeps repeating for about 2 days, until router runs ouf of memory and reboots :) I have no problems with CAPs that connect from other routers.

I have set local CAP configuration to Certificate: none, but the issue remains.

Any idea?
I've the same problem with multiple installations running 6.30.2 - did you ever find a solution to this problem? For me it seems to be as the local CAP receives the certificate but the issued certificate does not show as PrivateKey available. (Screenshot shows a CRS109 with Capsman shows CA Cert with 4C5E0CA5654C MAC and Issued_3 shows CAP with MAC 4C5E0CA5654C but no private key available)
2015-08-15_10-43-14.png
Screenshot of the certs of another CAP running on a different hardware shows correct behaviour - CAP Certificate with private key available:
2015-08-15_10-50-47.png
I guess due to this behaviour restarting the CapsMan / CAP prevents the CAP to access the certificate, reissue is no option as it's not possible to issue a cert with the same common name (which seems to be a bug itself,...?)

somebody able to shed some light?

BG Christoph

Re: CAPsMAN v2 ready for testing

Posted: Wed Sep 02, 2015 10:21 am
by Cornmeister
*second bump*
When I take a look at the logs, I see a lot of MAC addresses for all connecting clients.
is it possible to enter a description for these addresses to identify them ?

something like
12:08:15 caps,info IPhone6_A@AP_Switchruimte connected
12:08:21 caps,info IPhone6_A@AP_Woonkamer_Pa_en_Ma connected
12:08:21 caps,info IPhone6_A@AP_Switchruimte disconnected, registered to other interface
12:13:05 caps,info Samsung_Tab@AP_Switchruimte connected
12:26:38 caps,info Laptop@AP_Switchruimte connected
12:26:38 caps,info Laptop@AP_Woonkamer_Pa_en_Ma disconnected, registered to other interface
12:32:10 caps,info Laptop@AP_Woonkamer_Pa_en_Ma connected
12:32:10 caps,info Laptop@AP_Switchruimte disconnected, registered to other interface
instead of
12:08:15 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte connected
12:08:21 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma connected
12:08:21 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte disconnected, registered to other interface
12:13:05 caps,info D4:F4:6F:9B:EB:9A@AP_Switchruimte connected
12:26:38 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte connected
12:26:38 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma disconnected, registered to other interface
12:32:10 caps,info 8C:29:37:C1:02:1E@AP_Woonkamer_Pa_en_Ma connected
12:32:10 caps,info 8C:29:37:C1:02:1E@AP_Switchruimte disconnected, registered to other interface

Re: CAPsMAN v2 ready for testing

Posted: Tue Sep 29, 2015 9:18 am
by SirSiggi
I have constant problems with certificates when running CAPsMAN and CAP on the same router. Whenever I do a fresh configuration, issue new CA & certificates and join local CAP to CAPsMAN on the same router, things work fine. However, after reboot of the router, I am starting to get certificate errors. Apparently CAP is trying to locally install Certificates it gets from CAPsMAN, but fails to do so, since the certificates are already installed (well, it's the same router!). This process keeps repeating for about 2 days, until router runs ouf of memory and reboots :) I have no problems with CAPs that connect from other routers.

I have set local CAP configuration to Certificate: none, but the issue remains.

Any idea?
I've the same problem with multiple installations running 6.30.2 - did you ever find a solution to this problem? For me it seems to be as the local CAP receives the certificate but the issued certificate does not show as PrivateKey available. (Screenshot shows a CRS109 with Capsman shows CA Cert with 4C5E0CA5654C MAC and Issued_3 shows CAP with MAC 4C5E0CA5654C but no private key available)
2015-08-15_10-43-14.png
Screenshot of the certs of another CAP running on a different hardware shows correct behaviour - CAP Certificate with private key available:
2015-08-15_10-50-47.png
I guess due to this behaviour restarting the CapsMan / CAP prevents the CAP to access the certificate, reissue is no option as it's not possible to issue a cert with the same common name (which seems to be a bug itself,...?)

somebody able to shed some light?

BG Christoph
I'm having the same problem. As soon as I reboot the CAP, it cannot use the generated certificate anymore but can also not generate a new one, because there is already a certificate for that hostname. The client on another router just connects fine.

Re: CAPsMAN v2 ready for testing

Posted: Tue Sep 29, 2015 12:20 pm
by uldis
Please upgrade to the RouterOS v6.33rcX and then check again after you request a new certificate.

Re: CAPsMAN v2 ready for testing

Posted: Sat Oct 03, 2015 11:03 am
by bartjoo
Hello, i have installed Capsman on 1 server and have 50 clients.
Everything works great! Also the upgrades all together in one single click.
But could someone tell me how to upgrade the firmware (routerboard versions) with Capsman? otherwise i need to upgrade every client seperatly.
tnx for your reaction / advise!

Re: CAPsMAN v2 ready for testing

Posted: Sat Oct 03, 2015 11:05 am
by SirSiggi
Please upgrade to the RouterOS v6.33rcX and then check again after you request a new certificate.
It seems as if version 6.33rc16 solved the problem for me, at least for the first reboot. I will have an eye on it.

Re: CAPsMAN v2 ready for testing

Posted: Sun Oct 04, 2015 1:19 am
by juanvi
I think is not possible. I was looking for this too.

Re: CAPsMAN v2 ready for testing

Posted: Wed Oct 07, 2015 6:06 pm
by profek412
I have running Capsman v2 on CCR 1016-12G. I have ~500 interfaces. When connect >~150 users then after 5 minuts interfaces was inactive. After 1-2minutes they active to next 5 minutes. I tested 6.30.1 and 6.32.2.
On MT is capsman and hotspot. Bandwidth limit per user is 512kb. All traffic is ~20mb/15mb.

Do you have any idea? Mayby ~500 interfaces is too much?

Re: CAPsMAN v2 ready for testing

Posted: Wed Oct 07, 2015 7:16 pm
by Beone
Hi profek412;

We are running CCR-1009 running V6.33rc16 with 935 interfaces and 307 caps connected.

This because we regularly loose all caps from the management only to return a few minutes after; while there are no interruptions measured between the caps and capsman (all caps are coming from different locations and we have capsmans in different datacentres with different uplinks)

We have a case open with MT as we try to reproduce the problem.

BTW: do you also regulary see the message : 'disconnected, max key exchange retries'?

We have this at regular basis and then the Apple devices lock and need to be turned wifi off/on again for everything to function properly again until this happens again.

Re: CAPsMAN v2 ready for testing

Posted: Wed Oct 07, 2015 8:55 pm
by profek412
Hi profek412;

We are running CCR-1009 running V6.33rc16 with 935 interfaces and 307 caps connected.

This because we regularly loose all caps from the management only to return a few minutes after; while there are no interruptions measured between the caps and capsman (all caps are coming from different locations and we have capsmans in different datacentres with different uplinks)

We have a case open with MT as we try to reproduce the problem.
Tommorow I separates capsman and firewal to different routerboard. I think problem is in max load core cpu. When I reduce firewall and queue rules The problem is less common.
BTW: do you also regulary see the message : 'disconnected, max key exchange retries'?

We have this at regular basis and then the Apple devices lock and need to be turned wifi off/on again for everything to function properly again until this happens again.
I start system on Monday, and I don's see 'disconnected, max key exchange retries' in log. We tested system on iphone and we don't have any problem.

Re: CAPsMAN v2 ready for testing

Posted: Thu Oct 08, 2015 1:20 am
by Beone
For us, we already have a split between FW and CAPSMAN function between separate hardware devices...

For the Max retries, check your apple macos logs for the following error message:
kernel[0]: inputEAPOLFrame: Received non-key EAPOL frame

Drives me nuts... EAP tests on other vendor equipment are working correctly

Re: CAPsMAN v2 ready for testing

Posted: Wed Oct 14, 2015 2:48 pm
by mavink
We found a small bug in the latest (6.32.2) release. In webfig, when trying to copy a client to the access list (from the registrations tab in CAPsMAN v2) we get an internal server error and are redirected to the login screen. Doing the same thing with winbox works fine.

Re: CAPsMAN v2 ready for testing

Posted: Fri Oct 16, 2015 12:38 pm
by uldis
We found a small bug in the latest (6.32.2) release. In webfig, when trying to copy a client to the access list (from the registrations tab in CAPsMAN v2) we get an internal server error and are redirected to the login screen. Doing the same thing with winbox works fine.
Thank you for the report - we will try to fix it.

Re: CAPsMAN v2 ready for testing

Posted: Fri Oct 16, 2015 12:41 pm
by uldis
For us, we already have a split between FW and CAPSMAN function between separate hardware devices...

For the Max retries, check your apple macos logs for the following error message:
kernel[0]: inputEAPOLFrame: Received non-key EAPOL frame

Drives me nuts... EAP tests on other vendor equipment are working correctly
If you could provide us remote access to the CAPsMAN where this EAP test isn't working we could try to debug it.
We could need also instructions how to reproduce it on your remote location.
Please send that all to support@mikrotik.com

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 20, 2015 1:12 pm
by cleaver
Hello everyone!
I'm using CapsMan v2 on routeros 6.33.1 with several CAPs.
I noticed that the CapsMan registration table doesn't show "Last IP" info for connected stations. Caps don't seem to provide this information either. Is there a way, using CapsMan setup, to view "Last IP" info for connected stations?
When not using CapsMan, this info was available in the Registration table. But now it seems to be gone.

Thanks,
Kind regards!
Stoycho

Re: CAPsMAN v2 ready for testing

Posted: Fri Nov 20, 2015 8:32 pm
by juanvi
kick him with Access list and forcé quick roam
CAPsMAN is mostly meant for managing of access points in hotels, homes, apartments, offices etc. the clients in these places are windows and mac laptops, phones etc. 
I thing, you need more work about fast roaming in capsman 2

Wifi device need to lost of signal on cap1 to connect another cap2, but wifi device can work long time with cap1 on signal -89 even the cap2 is closer with signal -40

bleblas

Re: CAPsMAN v2 ready for testing

Posted: Mon Nov 23, 2015 3:12 pm
by Ridddick
We are massively deploying CAPSMANv2 now but are suffering controller cpu spikes to 100%.
Having the same issue, so sad. Using RB751 as a controller and grooves/caps as APs, ROS 6.34rc6. The controller takes 4 APs and have 50-100% CPU load and memory leakage. When 5th AP connects it just hangs up. I can't believe that controlling caps is so resource-intensive task. What am i supposed to do with that? Buy a CCR?

PS: I tried to turn off requesting a certificate.

Re: CAPsMAN v2 ready for testing

Posted: Mon Dec 14, 2015 4:35 pm
by anuser
Hi,

let´s add a sizing question. What kind of routerboard would I need for CAPSMAN with

~ 350x 802.11ac access points
~ 5000 clients concurrently connected (currently on my old platform and increasing)
~ 80000 sessions

Would a CCR1072 be enough? Should I wait for Cloud Hosted Router on some x86 server, instead?
(Btw, IPv6 traffic with CAPSMAN is running without any problems, right?)

Regards

Re: CAPsMAN v2 ready for testing

Posted: Wed Dec 16, 2015 5:41 pm
by Beone
We see the same thing on MIPS platforms running capsman having memleaks when hotspot and capsman is combined.
Case with MT opened, no feedback yet.

CPU resources for DTLS setup are important as well if you want to add quite an amount of CAPS to the CAPSMAN.

we've requested sizing notes to MT as well, but only received feedback that we should look at the forwarding capacity table to know how they the platforms scale.

PS; secondary bug: at bootup; almost all caps select 2412Mhz channel (not great)

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 12:54 am
by Test471
Are we going to get WMM support in CAPsMAN any time soon?

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 11:21 am
by juanvi
Are we going to get WMM support in CAPsMAN any time soon?
 What's new in 6.30 (2015-Jul-08 09:07):

*) wireless - added WMM power save suport for mobile devices; 

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 1:21 pm
by andriys
 What's new in 6.30 (2015-Jul-08 09:07):

*) wireless - added WMM power save suport for mobile devices; 
This has no relation to CAPsMAN.

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 1:44 pm
by Test471
Are we going to get WMM support in CAPsMAN any time soon?
 What's new in 6.30 (2015-Jul-08 09:07):

*) wireless - added WMM power save suport for mobile devices; 
Yes, but how do you turn it on on CAPsMAN configuration? I had 3 stand-alone APs working fine when I enable WMM on their interfaces but yesterday I put them to work as CAPs and now I cannot enable WMM. Looking at Registration table on CAPsMAN I can see that devices are not staying registered more than 2-3 minutes (only when they are in use).

So, how do I enable it?

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 2:39 pm
by juanvi
 What's new in 6.30 (2015-Jul-08 09:07):

*) wireless - added WMM power save suport for mobile devices; 
This has no relation to CAPsMAN.
You are right, sorry: This feature was enabled for capsman in 6.30 and revised in later firmwares because bugs.
What's new in 6.31 (2015-Aug-14 15:42):
*) wireless - improved WMM-PowerSave support in wireless-cm2 package

Test 471. It is enabled by default in CAPSMAN. No option for disable

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 4:29 pm
by Test471
Ok, but then, why are clients keep disconnecting after they go to sleep mode? As I said, I am looking at registration table on CAPsMAN and not a single client is registered for more than 3-5 minutes (except laptops):

- disconnected, received disassoc: sending station leaving (8)

All devices are running with cm2 package and v6.33.3. Before, when they were running as stand alone APs everything was fine (so, there was no other change except for setting up CAPsMAN).

Any ideas or hints?

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 5:35 pm
by uldis
- disconnected, received disassoc: sending station leaving (8)
This is wireless client decision to disconnect from the AP. We don't have any control why they want to connect.

WMM PowerSave feature is always enabled in the CAPsMAN and can't be disabled.

Re: CAPsMAN v2 ready for testing

Posted: Tue Jan 05, 2016 9:32 pm
by Test471
We don't have any control why they want to connect.
I guess you missed something. I said everything was working fine before CAPsMAN. In the meantime I tried some of those devices on another AP without CAPsMAN and it is working without disconnect.

How is that?

Re: CAPsMAN v2 ready for testing

Posted: Wed Jan 06, 2016 3:20 pm
by Test471
- disconnected, received disassoc: sending station leaving (8)
This is wireless client decision to disconnect from the AP. We don't have any control why they want to connect.

WMM PowerSave feature is always enabled in the CAPsMAN and can't be disabled.
Ok, now I am pretty sure there is some problem with CAPsMAN. I took one device (iPhone 6S with iOS 9.2) and connected it to CAP. It stays connected until it goes to sleep mode. Then I disabled CAP on that access point and configured it like stand alone AP. Then phone stays connected even when in sleep mode.

CAP = 951-2n
CAPsMAN = 750G

So, please have this checked or give me a hint what else is there to try?
We don't have any control why they want to connect.
Well, maybe not directly but if AP says to a client "No, I don't support WMM" and then client decided to disconnect because of that I would say it is one way of indirect control of client behaviour.

Re: CAPsMAN v2 ready for testing

Posted: Wed Jan 06, 2016 3:30 pm
by uldis
we need configuration for the CAPsMAN and for the Standalone AP.
Please send us the support output files from both to support@mikrotik.com.

Re: CAPsMAN v2 ready for testing

Posted: Mon Jan 18, 2016 12:09 am
by Test471
I've sent config to you the same day you asked for it.

In the meantime I did some testing and it looks like that clients are disconnecting fast when dhcp gives them very short lease. When DHCP is giving 60 seconds lease to clients then they are disconnecting. Now i changed it to 24h and they are not disconnecting.

Re: CAPsMAN v2 ready for testing

Posted: Tue Feb 09, 2016 4:57 pm
by whyfly
Are there any plans to specific data rates (ht-basic-mcs, supported-rates-b, etc) via CAPsMAN?

I would like to be able to allow only 24, 36, 48, 54, and HT MCS 3,4,5,6,7,11,12,13,14,15 on g/n 2.4 GHz, and only HT MCS 3,4,5,6,7 and VHT MCS 3,4,5,6,7,8,9 on n/ac 5 GHz on hAP ac lite wireless interfaces managed by CAPsMAN.

Re: CAPsMAN v2 ready for testing

Posted: Wed Feb 10, 2016 6:49 pm
by Beone
We asked this as well to increase wireless quality/roaming for 2.4Ghz clients. As using the access-lists RSSI Kick-method is incompatible with most MacOS devices (they get stuck!)

We got informed it's on the todo list, but i do not understand what makes this so difficult as it's already there in standalone modus.

Re: CAPsMAN v2 ready for testing

Posted: Thu Feb 11, 2016 8:34 pm
by lcffbr
In the configuration of CAPsMAN, one of the described steps is: Create bridge. What is the reason for this new bridge? In my configuration I already have a local-bridge that includes all Ethernet and Wlan interfaces, so every connection gets access to all network.. This required bridge in CAPsMAN has to be a different one? The third step is to add an IP address, DHCP Server and a masquerade rule to this bridge. Does it need to be different from the other bridge we already have?

Thanks in advance

LCFFBR

Re: CAPsMAN v2 ready for testing

Posted: Fri Feb 12, 2016 9:09 am
by karlisi
You can use any bridge if You integrate CAPsMAN in existing network.

Re: CAPsMAN v2 ready for testing

Posted: Tue Feb 23, 2016 6:20 pm
by dragelec
Hi profek412;

We are running CCR-1009 running V6.33rc16 with 935 interfaces and 307 caps connected.

This because we regularly loose all caps from the management only to return a few minutes after; while there are no interruptions measured between the caps and capsman (all caps are coming from different locations and we have capsmans in different datacentres with different uplinks)

We have a case open with MT as we try to reproduce the problem.

BTW: do you also regulary see the message : 'disconnected, max key exchange retries'?

We have this at regular basis and then the Apple devices lock and need to be turned wifi off/on again for everything to function properly again until this happens again.
Hi, I have the same issue, my capsman run on CCR-1036 v6.34.2 with 160 interface and 80 caps connected. Capsman regularly loose all caps from the management only and then return a few minutes after. This issue appear every about 4hours, after loose times my capsman auto reboot. :(. I'm so tired to find out what error.
Did you fixed it?
tks

Re: CAPsMAN v2 ready for testing

Posted: Wed Feb 24, 2016 9:09 pm
by Beone
We havent fixed this, we are currently on v6.35rc12 for the memory leak issue we had massive issues with (router runs out of memory and then reboots)

Re: CAPsMAN v2 ready for testing

Posted: Thu Mar 10, 2016 1:10 pm
by anuser
With CAPsMAN v2 package and new "wireless-rep" package IPv6 for clients is lost, i.e.

o problem: with CAPsMANv2 and „wireless-rep“ package clients don´t receive any IPv6 traffic, no IPv6 router adverisements at all iff VLAN assignement is done dynamically. Dynamic VLAN assignment within datapath works for IPv4 traffic, though. If I assign a VLAN ID wihin datapath configuration of CAPSMAN, IPv6 and IPv4 is working without any problems.

(with traffic forwarding @CAPSMAN controller)
Image

[UPDATE]
+ It works when I change multicast-helper setting to full on the Cap interface

Re: CAPsMAN v2 ready for testing

Posted: Fri Jun 10, 2016 1:41 am
by SolarW
+1 to this improvement
Hello everyone!
I'm using CapsMan v2 on routeros 6.33.1 with several CAPs.
I noticed that the CapsMan registration table doesn't show "Last IP" info for connected stations. Caps don't seem to provide this information either. Is there a way, using CapsMan setup, to view "Last IP" info for connected stations?
When not using CapsMan, this info was available in the Registration table. But now it seems to be gone.

Thanks,
Kind regards!
Stoycho

Re: CAPsMAN v2 ready for testing

Posted: Sat Jun 25, 2016 11:12 pm
by joncolby
I would like NV2 with encryption on capsman.

Re: CAPsMAN v2 ready for testing

Posted: Thu May 03, 2018 4:00 pm
by southgate
+1 on the nv2 support. We have a network of ca 50 devices where each has a 3 connected bridged sectors and capsman would be a nice feature to centralize the management since our clients are mostly routeros