CAPSMAN with nothing but 2.4ghz gear, fine, easy, neat
However 2.4ghz and 5ghz devices is a total mess and a pain in the ass, but maybe there's something i'm missing? (i'm hoping so)
It's really simple, I just want 2.4ghz and 5ghz with the same name, but obviously subtle differences like 20mhz channel width with 2.4ghz and 20/40mhz with 5.0ghz. Limited to certain channels so as to not overlap
The problem is I can't do this with a single config. I need to duplicate every.... single.......... entry........... because anything that contains the typical 2.4ghz channel list of 1/6/11 causes 5ghz to fail completely because of invalid frequency. Leaving it on auto sucks because 2.4ghz channels are all over the place, and I also can't leave channel width on auto because 80mhz on 5ghz is terrible, as is 20/40mhz on 2.4ghz. These are the defaults
Also need to duplicate all provisioning and add Hw Supported Mode
This is rubbish, surely there's a better way? A lot of our deployments contain more than 100 different SSID's (unique for each room) - Swapping out WAP's with WAP AC's means adding a lot of extra config to the router
And thirdly there's a problem with 2.4ghz and 5ghz being treated as completely separate interfaces and CAPS tunnels. So they cannot talk to each other, a PC on 5ghz will not be able to print to a printer on 2.4ghz with the same network name due to bridge horizon rule. Changing to local forwarding mode is not ideal and creates yet another mess