Starting from 6.30 it's included in main package.where do I find cm2 package for 6.30 6.30.1?
didn't find it on the download page.
Thanks, so i'm going to update.Starting from 6.30 it's included in main package.where do I find cm2 package for 6.30 6.30.1?
didn't find it on the download page.
Was this issue resolved? I'm having exactly the same problem.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?
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 likeinstead ofCode: Select all12: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
Code: Select all12: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
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)"Was this issue resolved? I'm having exactly the same problem.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)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?
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 likeinstead ofCode: Select all12: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
Code: Select all12: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
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.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)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?
Screenshot of the certs of another CAP running on a different hardware shows correct behaviour - CAP Certificate with private key available:
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
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.Please upgrade to the RouterOS v6.33rcX and then check again after you request a new certificate.
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.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.
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.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.
Thank you for the report - we will try to fix it.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.
If you could provide us remote access to the CAPsMAN where this EAP test isn't working we could try to debug it.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
I thing, you need more work about fast roaming in capsman 2CAPsMAN 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.
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
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?We are massively deploying CAPSMANv2 now but are suffering controller cpu spikes to 100%.
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;
This has no relation to CAPsMAN.Code: Select allWhat'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).Are we going to get WMM support in CAPsMAN any time soon?Code: Select allWhat's new in 6.30 (2015-Jul-08 09:07): *) wireless - added WMM power save suport for mobile devices;
You are right, sorry: This feature was enabled for capsman in 6.30 and revised in later firmwares because bugs.This has no relation to CAPsMAN.Code: Select allWhat's new in 6.30 (2015-Jul-08 09:07): *) wireless - added WMM power save suport for mobile devices;
What's new in 6.31 (2015-Aug-14 15:42):
*) wireless - improved WMM-PowerSave support in wireless-cm2 package
This is wireless client decision to disconnect from the AP. We don't have any control why they want to connect.- disconnected, received disassoc: sending station leaving (8)
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.We don't have any control why they want to connect.
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.This is wireless client decision to disconnect from the AP. We don't have any control why they want to connect.- disconnected, received disassoc: sending station leaving (8)
WMM PowerSave feature is always enabled in the CAPsMAN and can't be disabled.
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.We don't have any control why they want to connect.
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.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.
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