When creating a separate DHCP server instance for wlan2 that line in the table appears in red: invalid. "RouterOS by Example" (2nd Ed., p. 25) states that an interface placed on or removed from a bridge makes the DHCP server for that interface invalid. Is the Mode selection of "AP Bridge" invalidating the DHCP server? Is the order of setting up various windows critical? Of the modes in the drop down menu in the "Interface <wlan2>" window there isn't an obvious choice for a mode to set up a wi-fi radio on its own subnet. What am I missing?
I think the reason why you're having trouble with the DHCP Server is because "wlan2" is still in listed in RouterOS's Bridge>bridge1>Ports — "wlan2" (assuming that the "lab wifi") should NOT be a port in what I describe. Pretty sure you want "AP Bridge" – there, the word bridge in name refers to the fact it handles multiple wireless clients (which is was APs do: they "bridge" all connected wireless devices, but on that interface only). With "station mode" is the reverse of "ap bridge" - that's a
single connection to another Wi-Fi AP, and you'd typically have a DHCP Client on a "station" to
pull an address from another network/subnet. With all the other Wi-Fi modes to deal stuff in-between.
To bridge a wi-fi interface, with other ethernet ports/tunnels/etc, that requires the wifi being listed as a "port member" of a
RouterOS bridge. And, a wi-fi interface is a "separate subnet" automatically, unless it's it's in bridge. (e.g. "/interface bridge ports print" should NOT show wlan2 here).
I'd recommend you post your config, easier for everyone to comment on your actual config. Pretty sure you're a few lines away from your diagram. "/export hide-sensitive" is the command to get a config, without passwords.
how to setup the router is easily accomplished with VLANS as per this article which has an example for your case.
viewtopic.php?t=143620
one bridge,
ethernet ports and wlans on bridge
proper bridge vlan config.
Pretty much done!
To be fair, "easily accomplished with VLANS", may be over-selling
. But @anav has a point, if you're familar with cisco-style switch config, and want to do a deep-dive into Mikrotik's bridging @pcunite's VLAN guide is great. It's a bit complex, so not for everyone. In the cisco/@avnu/@pcunite scheme, your wlan2 should be a bridge port, as should all your interface. Instead of assigning an IP address directly to the wlan2 interface, you'd use a new VLAN to do that, still likely need a DHCP Server too.
e.g. in the
viewtopic.php?t=143620 scheme, you create a VLAN interface for the 192.168.200.0/24 network, and use say vlan-id=200 – then use Bridge>bridge1>VLANs to assign wlan2 to the VLAN 200. More complex than that, but that's the gist of the different approach. Since all interfaces use the bridge, it could be slower depending on the exact config/device since "hardware offloading"/"fast path" support varies.
To some people, this is more natural approach & to others, it adds an unnecessary level of indirection and make the config unnecessary complex. My opinion is if you're familiar with VLAN, this approach makes sense & if VLANs are mystery, there is an additional learning curve.
The nice part about Mikrotik is the a lot ways to do stuff & the bad part is there a lot of ways to do stuff.