Environment: RouterOS v6.42.5 (stable) on 2011UiAS-2HnD and cAP ac under CAPsMAN

GOAL: I want two separate SSIDs, each on one band. So, one on 2.4G and one on 5G. What I have now is both SSIDs on both 2.4 and 5

There are some seemingly odd things I do not understand (yet.)

The main CAP interface shows up as "inactive" but four interfaces (CAP3-6) appear on the list and correspond to the cAP ac MACs. Cap 3 and Cap 5 are for the main config SSID and CAP4 and 6 are for the alternate SSID.

There is no CAPsMAN CAP interface table entry for the local WLAN interface. That interface shows as disabled and managed by CAPsMAN in /interface wireless print. I've added the route suggested by https://wiki.mikrotik.com/wiki/Manual:S ... in_CAPsMAN even though my WLAN1 is on the same bridge at the cAP ac (which CAPsMAN can see.) This has had no effect I can detect. The local WLAN worked as a local wireless interface before transitioning to CAPsMAN. It doesn't do anything now. While I suspect a switching problem I do not have any ideas how to diagnose it.

Configuration:

I have separate configurations (and Security Configs) for the master and alternate SSIDs. The master configuration in the provisioning entry restricts operating band of all configurations **if** that is set in the configuration. If not set, it seems to override the band selections in the slave configurations - the alternate configuration SSIDs show on all bands even if the alternate configuration only specifies one band and the master has no band specified.

QUESTIONS:

What am I missing here? How do I restrict SSIDs by band in CAPsMAN?

Any suggestions about how to figure out why the local WLAN is not playing nice? I don't know how to collect any useful diagnostic data for this.

Thanks in advance for any help you can provide.

Not that this adds much value, but the router log is flooded with:

16:46:12 caps,info CAP failed to join MikroTik (::ffff:192.168.47.10:5246)
16:46:20 caps,info CAP selected CAPsMAN MikroTik (::ffff:192.168.47.10:5246)
16:46:40 caps,info CAP connect to MikroTik (::ffff:192.168.47.10:5246) failed: timeout
16:46:40 caps,info CAP failed to join MikroTik (::ffff:192.168.47.10:5246)
16:46:47 caps,info CAP selected CAPsMAN MikroTik (::ffff:192.168.47.10:5246)
16:47:07 caps,info CAP connect to MikroTik (::ffff:192.168.47.10:5246) failed: timeout
16:47:07 caps,info CAP failed to join MikroTik (::ffff:192.168.47.10:5246)
16:47:15 caps,info CAP selected CAPsMAN MikroTik (::ffff:192.168.47.10:5246)
16:47:33 dhcp,info dhcp deassigned 192.168.47.109 from 94:E9:6A:48:AF:04
16:47:34 dhcp,info defconf assigned 192.168.47.109 to 94:E9:6A:48:AF:04
16:47:35 caps,info CAP connect to MikroTik (::ffff:192.168.47.10:5246) failed: timeout
16:47:35 caps,info CAP failed to join MikroTik (::ffff:192.168.47.10:5246)
16:47:43 caps,info CAP selected CAPsMAN MikroTik (::ffff:192.168.47.10:5246)
16:48:03 caps,info CAP connect to MikroTik (::ffff:192.168.47.10:5246) failed: timeout
16:48:03 caps,info CAP failed to join MikroTik (::ffff:192.168.47.10:5246)
16:48:10 caps,info CAP selected CAPsMAN MikroTik (::ffff:192.168.47.10:5246)

192.168.47.10 is the router IP.

I have simply created two provisioning rules that match each Radio MAC (thus each band inside the same AP)

Each rule points to a different Master Configuration with its own SSID (no need for slave configuration, I use them for multiple SSID inside the same band if needed)

No luck so far. Still having a problem getting SSIDs restricted to a single band, and CAPsMAN not seeing local WLAN interface.

The remote AP is cAP ac (dual band) I have several, I'm just trying to get the first one running before I add to the complexity of additional units.

If I use a single provisioning file with a master config with no band information and slave config with band information, I end up with both SSIDs on both bands, and I do not know why.

If I use two separate provisioning files with a single master config with a band specified in each, I only see one SSID on the band of the first provisioning file, the interface associated with the other provisioning file band reports "no supported channel" and nothing on that band.

What am I missing? As I understand it, the provisioning file that matches the capability of the AP should result in an interface that is the logical 'and' of the provisioning file, config, and security config, logically "or" 'd with the capability of the physical radio. I'm clearly missing something here, can you tell me what? Or point me to documentation or diagnostic suggestions?

Thanks in advance for any help you can provide.

Got this working. the appropriate spells and incantations are from this older post:

viewtopic.php?t=125026

and here is my reply summarizing the results to another:

viewtopic.php?f=7&t=136476

The part I was missing is the need to set up channel selections. And you need to set up configurations that select those channels. Finally, you need to set up provisioning so that hardware modes are selected.

That was, basically, what I suggested you to do......

You have chosen two provisioning rules , based on hw-supported-modes rather than mac-address of each radio....

Mine was:

add action=create-dynamic-enabled master-configuration=cfg_5g name-format=identity radio-mac=6C:3B:6B:xx:xx:xx
add action=create-dynamic-enabled master-configuration=cfg_2g4 name-format=identity radio-mac=6C:3B:6B:xx:xx:xx

This way you can get more flexibility, adding more wanted configurations "per access point" rather than a single one "per supported modes" that matches multiple AP at one time.

Yes, but your advice misses some key steps that seem to be required for correct operation, like the fact that the channel file is apparently required.

I already had two provisioning rules, and selecting the specific MAC had no effect. The addition of channel files and references to them in the provisioning files made the difference for me.

I do appreciate your answer. While helpful, it did not solve my problem by itself.

I don't have any channel configuration.
The fact you have an SSID configuration that matches a RADIO MAC address, means that configuration, thus that SSID will be used only on THAT radio.

So
5GHz radio = aa:bb:cc:dd:ee:01 = config01 = SSID_A
2.4GHz radio = aa:bb:cc:dd:ee:02 = config02 = SSID_B

simple, it's strange you can't get it working this way , but If you are ok with your solution it is enough..

<t>That is odd that you don't have a channel file and I seem to need one. It may be a case of "five ways to peel an apple" and we both have a way. I'd like to see your CAPsMAN export if you have time to post it. I just posted my to a related thread:

viewtopic.php?f=7&t=136476


Thanks,
Rich