+1 for Last-IP2) In registration all information should be visible like in normal mode (last-ip, routeros version etc.)
I'm not sure but i think is the same for CAPSMAN. At the end you have one ap and is remotelly controlled.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.
Uldis said: "you need RouterOS Level 4 licenese to make a board as a CAP AP.I'm not sure but i think is the same for CAPSMAN. At the end you have one ap and is remotelly controlled.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 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.
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?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?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.
No, this is not correct. When he gets a connection with CAPsMAN again, he will send the WiFi signal again.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.
could you tell more about your infrastructure and mikrotik OS / Capsman version?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!
Hmm, could you upload a image of your settings for CAPsman?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!
Using wireless-cm2 package and connected via MAC.are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?
could you try it with IP addresses? I work with IP's and it works fine.Using wireless-cm2 package and connected via MAC.are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?
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!
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.could you try it with IP addresses? I work with IP's and it works fine.Using wireless-cm2 package and connected via MAC.are you using wireless-fp package or wireless-cm2 package?
The CAPs are connected to CAPsMAN via MAC connection or IP connection?
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!
one solution is manipulating datarates, disabling slower datarates client jump to another AP before reaching such lower signal level.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
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.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
Please contact support@mikrotik.com about this problem and also tell us how you are measuring the performance.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
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)
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: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 ?
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.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
http://www.mikrotik.com/download/share/ ... mipsbe.npkHi!
Where can I get package of CAPsMan v2 for 6.29 (RC20)? in all_files is not there..
Thank you.
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
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
Answered in post 13 of the first page of this thread:Why cannot v1 CAPs connect to v2 CAPsMAN or vice-versa? Aren't CAPsMAN v1 and v2 both RFC5416 (CAPWAP) compliant?
-- Nathan
Very interesting, could someone share info about how this "improved logging entries when client roams between the CAPs"
MegaThanxIt 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
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