CAPsMAN with two bridges

RouterOS Beginner Basics
1

Greetings. It’s been a while since I’ve been running MikroTik, lots of things changed, and I am stuck with some newbie questions.

Basically, I am trying to set up home network, but to use 2 bridges. So I created new bridge, assigned it to configuration, and when I connect to SSID that configuration provisioned I am still getting the IP from dhcp server on master configuration bridge.

Searched a lot, and I can’t quite figure out what am I doing wrong here. Export from CAPsMAN router attached. Thanks!
router.rsc (8.61 KB)

2

Why 2 bridges ?
You only need 1.

3

My understanding is that if I only use one, then I’d have to use VLANs, and that quickly complicates things. I would like to avoid that.

So, is it possible to have 2, or even more, bridges? I am under impression my configuration should just work, even if it’s not super optimal.

4

When using CAPsMAN to provision remote CAPs, datapath is applied remotely (there is no such thing as capsman forwarding in new wifi capsman anymore). Which means that CAP devices need bridge-guest pre-existing, CAPsMAN only provisions wifi radio but doesn’t add/adjust other config.

And then, when you think about connecting bridge-guest entities on all devices (router and all CAPs), it becomes clear that you probably do need VLANs to properly separate traffic of guest network on “backbone”.

5

Ah, I see, I didn’t know this! So that’s why I wasn’t able to find local-forwarding setting in my CAPsMAN configuration.

Okay, seems to me that I don’t need CAPsMAN at all, I think I will set up each AP manually, since I’ll have to do it anyway. Especially since CAPsMAN tends to recreate virtual wifis with incrementing id’s on each change (currently on one AP I have wifi10) so I would have to re-setup everything on each CAPsMAN change.

Thank you for helping clearing this for me and moving me from wrong CAPsMAN path.

6

That’s a setting in capsman and you do not need to setup everything again.
Either you keep the numbering constant (create enabled) or you keep it dynamic (create dynamic enabled).
In both cases you should not have to worry about provisioning and/or settings.

Action to take if rule matches are specified by the following settings:
create-disabled - create disabled static interfaces for radio. I.e., the interfaces will be bound to the radio, but the radio will not be operational until the interface is manually enabled;
create-enabled - create enabled static interfaces. I.e., the interfaces will be bound to the radio and the radio will be operational;
create-dynamic-enabled - create enabled dynamic interfaces. I.e., the interfaces will be bound to the radio, and the radio will be operational;
none - do nothing, leaves radio in the non-provisioned state;

7

Got it. Yes, that makes sense, just tried and it works as you described. Thanks! Now onto figuring out VLANs with this setup!