Hello Guys,
we have a few wireless networks that all consist out of cAP AC Access Points. Either one of the APs or the Router is the CAPsMAN. We had them configured with multiple Configurations that had multiple SSIDs. Since the last RouterOS Update (6.48.5 long-term or 6.49 stable) the APs only have one interface enabled. When you look in the CAPsMAN Interfaces list, all the inactive interfaces (either all 5G or all 2.4G) have an error "no supported channel". When you connect to one of the APs directly, one of the wireless interfaces is disabled and there's a virtual interface for other SSIDs that should send on the other frequency. So basically when you have two different SSIDs for your 2.4G and 5G Network, the 5G Network would try to send on the 2.4G interface.
We tried a lot of different configurations (manually setting frequency, bands, channels, etc.) but the only thing that worked was to configure the Hw. Supported Modes in the provisioning of the APs to all available. We then provisioned all the APs and they were able to select a channel on the right interfaces, but they didn't send a SSID. So you had to double-click every interface and select a configuration for it. This works fine so far, but you can only select one Configuration, that only has one SSID.
We weren't able to solve this issue so far, the only thing we can say is that all our customers that have Mikrotik cAP ACs have this issue.
I attached some screenshots of our configurations. The "befores" are from another customer so dont wonder why the names are different.
It would be great, if someone could provide me a solution here.
Thank you in advance!
CAPsMAN error no supported Channels
You do not have the required permissions to view the files attached to this post.
Re: CAPsMAN error no supported Channels
Think you can't use master/slave on two different radios.
Can you please share your /caps-man export hide-sensitive?
And please use the code tags to make it more readable.
Can you please share your /caps-man export hide-sensitive?
And please use the code tags to make it more readable.
Re: CAPsMAN error no supported Channels
Hello,
thank you for your quick answer!
When i run /caps-man export hide-sensitive on the AP that is the caps-man i get:
thank you for your quick answer!
When i run /caps-man export hide-sensitive on the AP that is the caps-man i get:
Code: Select all
[admin@AP10] > /caps-man export hide-sensitive
# nov/02/2021 11:32:46 by RouterOS 6.49
# software id = A4DX-BB69
#
# model = RBcAPGi-5acD2nD
# serial number = B9320A9B5567
/caps-man channel
add band=2ghz-b/g/n name=2G
add band=5ghz-a/n/ac name=5G
/caps-man security
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm name=DAT@Gast
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm name=DAT@JOB
/caps-man configuration
add channel=5G datapath=DP-DATAJOB datapath.bridge=bridge datapath.client-to-client-forwarding=no datapath.local-forwarding=yes mode=ap name=intWLAN-5G security=DAT@JOB ssid=DAT@JOB
add channel=2G datapath=DP-DATAJOB datapath.bridge=bridge datapath.client-to-client-forwarding=no datapath.local-forwarding=yes mode=ap name=intWLAN-2G security=DAT@JOB ssid=DAT@JOB
/caps-man datapath
add bridge=bridge local-forwarding=yes name=DP-DATAJOB
add bridge=bridge name=DP-GAST
/caps-man interface
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=74:4D:28:C2:0C:66 master-interface=none name=cap1 radio-mac=74:4D:28:C2:0C:66 radio-name=744D28C20C66
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=74:4D:28:C2:0C:65 master-interface=none name=cap2 radio-mac=74:4D:28:C2:0C:65 radio-name=744D28C20C65
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=74:4D:28:C1:D8:9D master-interface=none name=cap349 radio-mac=74:4D:28:C1:D8:9D radio-name=744D28C1D89D
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=74:4D:28:C1:D8:9E master-interface=none name=cap350 radio-mac=74:4D:28:C1:D8:9E radio-name=744D28C1D89E
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=74:4D:28:C2:0B:FF master-interface=none name=cap351 radio-mac=74:4D:28:C2:0B:FF radio-name=744D28C20BFF
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=74:4D:28:C2:0C:00 master-interface=none name=cap352 radio-mac=74:4D:28:C2:0C:00 radio-name=744D28C20C00
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:D0 master-interface=none name=cap353 radio-mac=2C:C8:1B:66:C9:D0 radio-name=2CC81B66C9D0
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:D1 master-interface=none name=cap354 radio-mac=2C:C8:1B:66:C9:D1 radio-name=2CC81B66C9D1
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:DC master-interface=none name=cap355 radio-mac=2C:C8:1B:66:C9:DC radio-name=2CC81B66C9DC
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:DD master-interface=none name=cap356 radio-mac=2C:C8:1B:66:C9:DD radio-name=2CC81B66C9DD
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:E8 master-interface=none name=cap357 radio-mac=2C:C8:1B:66:C9:E8 radio-name=2CC81B66C9E8
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:E9 master-interface=none name=cap358 radio-mac=2C:C8:1B:66:C9:E9 radio-name=2CC81B66C9E9
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:9C master-interface=none name=cap359 radio-mac=2C:C8:1B:66:C9:9C radio-name=2CC81B66C99C
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:9D master-interface=none name=cap360 radio-mac=2C:C8:1B:66:C9:9D radio-name=2CC81B66C99D
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:90 master-interface=none name=cap361 radio-mac=2C:C8:1B:66:C9:90 radio-name=2CC81B66C990
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:91 master-interface=none name=cap362 radio-mac=2C:C8:1B:66:C9:91 radio-name=2CC81B66C991
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:C4 master-interface=none name=cap363 radio-mac=2C:C8:1B:66:C9:C4 radio-name=2CC81B66C9C4
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=2C:C8:1B:66:C9:C5 master-interface=none name=cap364 radio-mac=2C:C8:1B:66:C9:C5 radio-name=2CC81B66C9C5
add configuration=intWLAN-5G disabled=no l2mtu=1600 mac-address=74:4D:28:C2:0C:24 master-interface=none name=cap365 radio-mac=74:4D:28:C2:0C:24 radio-name=744D28C20C24
add configuration=intWLAN-2G disabled=no l2mtu=1600 mac-address=74:4D:28:C2:0C:23 master-interface=none name=cap366 radio-mac=74:4D:28:C2:0C:23 radio-name=744D28C20C23
/caps-man manager
set ca-certificate=auto certificate=auto enabled=yes
/caps-man provisioning
add action=create-dynamic-enabled disabled=yes hw-supported-modes=a master-configuration=intWLAN-5G
add action=create-dynamic-enabled disabled=yes slave-configurations=intWLAN-2G
add action=create-dynamic-enabled hw-supported-modes=ac,a,b,g,gn,a-turbo,g-turbo master-configuration=intWLAN-5G slave-configurations=intWLAN-2G
I don't really understand what you meant there. Do you mean you can't use a master and a slave configuration on two different interfaces?Think you can't use master/slave on two different radios.
Re: CAPsMAN error no supported Channels
Each radio can either be 5g or 2g. You need a separate provisioning rule/entry for each radio. This means a dual band device would need 2 separate rules.
Re: CAPsMAN error no supported Channels
So the solution is to have two separate provisionings for the 5g configuration and the 2G configuration?
Re: CAPsMAN error no supported Channels [SOLVED]
Ok, first off all thank you very much for your help! 
I got it working the way i wanted it to by making two configurations that only set hardware configuration (band, channel, frequency,...) and used those as master configs on the two provisionings. Then i changed my old configurations for the two SSIDs to only set "software" configurations (SSID, Datapath, etc.) and used those as the slave configs on the two provisionings. Works perfectly fine!
I got it working the way i wanted it to by making two configurations that only set hardware configuration (band, channel, frequency,...) and used those as master configs on the two provisionings. Then i changed my old configurations for the two SSIDs to only set "software" configurations (SSID, Datapath, etc.) and used those as the slave configs on the two provisionings. Works perfectly fine!
Re: CAPsMAN error no supported Channels
Advanced mode \ Skip DFS cahnnels = disabled.
works fine for country = "ETSI 5.5-5.7 outdoor"
Mikrotik respects EU regulations, which demand DFS and TPC for all outdoor and some indoor channels. But the default setting is to skip channels demanding DFS (may be a bug). As soon as all the outdoor channels demand DFS, you have to allow using DFS-demanding channels or you get the "no supported channel" error. Consult the wiki page, scroll down to "Caption" table https://en.wikipedia.org/wiki/List_of_W ... j/n/ac/ax)
works fine for country = "ETSI 5.5-5.7 outdoor"
Mikrotik respects EU regulations, which demand DFS and TPC for all outdoor and some indoor channels. But the default setting is to skip channels demanding DFS (may be a bug). As soon as all the outdoor channels demand DFS, you have to allow using DFS-demanding channels or you get the "no supported channel" error. Consult the wiki page, scroll down to "Caption" table https://en.wikipedia.org/wiki/List_of_W ... j/n/ac/ax)