That example you link to is for legacy capsman / wifi.
That will not work.
In wifiwave2 capsman there is also no central forwarding anymore, only local forwarding.
On device acting as cap, you don't specify datapath.
Only on the controller (there is a tab for it in the Wireless menu, hard to miss).
Check this page for better reference (CLI only but should be obvious where you need to go, with and without vlan)
https://help.mikrotik.com/docs/display/ ... ionexample:
And ... if you are using that AC3 as controller AND AP, that will not work either in wifiwave2 capsman.
You need to configure the interfaces locally on that device.
How many APs are you controlling in that capsman controller ?
If only 1 to 4, it may be a lot easier to handle it locally per device (unless you consider it a learning project).
Just my view.
It's a little weird now how capsman is buried under remote cap. Capsman is the main reason I recommend Mikrotiks and the UX has made further regressions.
Personal opinion: I had little to no trouble getting used to wifiwave2 environment since it more or less took over the same structure from legacy capsman.
Set channels
Set Security
Set datapath (if needed)
Set config
Apply config to interface.
