Thanks for the feedback.We have some ideas for new web interface for The Dude. However at the moment there is no known date on when this new web interface might get implemented and in what form it will come. Note that it will not be re-implementation of old web interface.
+1Please, return web access feature. Only these stops to migrate dude from windows to CCR. Enything else what we need is worked in 6.35.2 on CCR1016.
You cant move a client from one AP to another, but you can use access-list to kick users with low signal . This will trigger the users equipment to search for the SSID again and will (hopefully) connect to the best one.
Using cm2juanvi - Do you use wireless-rep package?
[juanvi@xxx] /caps-man> configuration set channel.band= 2ghz-b 2ghz-b/g 2ghz-b/g/n 2ghz-onlyg 2ghz-onlyn 5ghz-a 5ghz-a/n 5ghz-a/n/ac 5ghz-onlyac 5ghz-onlyn
Mmmm.... Interesting!!! Hotspot 2.0 with HTTPS-Redirection and another new features in the last 6.35rc7
[img]https://www.dropbox.com/s/15zj0l5au84gk ... 9.png?dl=0[/img]
SOLVEDTrying to drag and drop .npk files from win7 intro ROs packages window for upgrading and it is not possible. Working well with Winbox2.
As client do from captive portal side but from cli. Useful for scripting too if you want start counting login star time since x.*) hotspot - added option to login user manually from cli;
Can someone explain this please
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;
You can force roaming and the device has nothing to do with that. Devices does not apreciate when ap has changed. For them, the ap is always the same!What do you mean by thatYou can fine tunning roaming using accest lists
juanvi - Please first test with different browser and/or clear cache.
juanvi - Here is sign-up form with phone number
Is this related to [Ticket#2015073166000411] Lost capsman confing when upgrading ?6.33rc3 is released.
*) tile - fixed occasional deadlock on module unload;
tried rc12 too from rc10 and the same bad result. CAPSMAN DISABLED AFTER UPGRADE. Supout sended.Downgraded to v6.31rc10 and then upgraded to v6.31rc12 with bundle package - CAPsMAN works ok (no configuration lost),test 6.31rc10 to 6.31rc11 using single .npk's as i used to.
Does not work. No wireless interfaces in my CAPsMAN (CCR).
/interface wireless set 0 wmm-support=enabled
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?