I have 2 Cap Ac Rbcapgi-5acd2nd and 1 RB750Gr3 as my router.. the Cap’s is used only as Wifi AP. Now I’m using capsman to manage the network (internal and guess) and the other configs… I saw one video telling about is not good to have 2 APs in the same channel, and now my cap’s are using the same channel.
So, my question is: is there a way on the capsman to set a different channel or I need to remove capsman and config one by one… or… leave there and the routeros knows how to deal with the channels?
Why would there be a problem with the same channel.
You clearly are a radio genius, and having them on the same channel magnifies their propagative properties 10fold such that any user in the House will not see any outside AP devices and will only see the two inside devices.
Furthermore, the devices using wifi will flip back and forth between the two APs, without missing a beat as the router stitches together the packets together so it appears as one signal doubling the speed of your connection.
If the max bandwidth is wanted, then running the 2 CAP ac on different channels is the way to go. Still use only channel 1, 6 or 11, with 20MHz width, to have non-overlapping channels.
Having the same SSID on different channels is no problem for the clients, and gives the max aggregated throughput, as air-time for each channel is used, and there is no air-time-sharing between channels.
For CAPsMAN performance do use “local forwarding”, to avoid the CAPWAP tunnel connection for data between the CAP and CAPsMAN.
I do not trust the “auto” channel selection in CAPsMAN or in standalone mode. Take control, check your environment (e.g. Snooper tool) and make a wise channel selection.
You probably will have to make dedicated configurations in CAPsMAN for each CAP, to set different channels.
I can’t say how it is for anyone, but the use of “local forwarding” normally works for me only on “simple” network building schemes. In the case. when access points are “scattered” over the network and located behind several switches, everything works much easier, if this option is disabled. With the “local forwarding” option disabled, all wireless network interfaces are located “in one place” - on the CapsMan server. MAC addresses of clients are always “in the same device” at the same time. IMHO, somehow everything works “more clearly”. I may not be using low performance devices as a CapsMan server, but I’ve had no problems with client speeds over the air.
I have 35 hAP ac/wAP ac , with 20 switches (RB260GSP) and 20 SXTsq PtMP wifi links, over 4 Powerbox, as one LAN, 4 VLAN/ 4 SSID.
No CAPsMAN. But Local tuning of hAP/wAP for faster roaming and reduced interference. Works fine, client net data rate is typical 180 Mbps in every corner of the area on 5GHz/40MHz channels.
Central monitoring like registration table and logging via DUDE. One RADIUS server. No scheduled reboots.
“It’s better to use CAPSMAN or not?” It depends on what you want to do, and there are “features” in CAPsMAN that are usefull in certain setups (like AP load balancing).
Some are dangerous for performance, like the scheduled channel re-selection, CAPWAP tunnel to CAPsMAN router overhead and potential fragmentation, lack of full control on the wlan interface (WMM, AMSDU, AMPDU)
So far my experience without CAPsMAN. No plans to change that.
One CAPsMAN question still open. Is “priority” transmitted over the CAPWAP tunnel,? It’s needed for using WMM properly. Without WMM or priority set you only do “best effort” timing, and that is the slowest way to get an wifi air-time slot. WMM capable AP might grab that slot before you are ready with the countdown.