Assistance with hEX S and Audience WIFI over VLAN

Hi All,

I have hEX S as my home router and 2 Audience units.
I would like to configure them so the Wireless clients will be part of a specific VLAN - 200.

Currently, my hEX S router is connected to a single Audience AP with RouterOS 6 installed.
Wifi + VLAN are configured well, everything works fine.

But I would like:
A. To setup a Mesh wifi (as I don’t have wifi signal everywhere at my apartment)
B. Update the Audience RouterOS to the latest stable version.

I configured the Wireless Datapath VLAN parameter, but it seems that it is not supported anymore with RouterOS 7, How can I solve it? Am I doing anything wrong?

BTW, I’m using the wifi-qcom-ac package with my Audience devices.
I would not like to use CAPsMAN as I understood it does not support Mesh wifi.
My end goal is to have a Mesh wifi (single, extended wifi - using the same SSID and network configuration) between both Audience devices.

Related Router configuration

# RouterOS 7.19.4

/interface bridge
add admin-mac= auto-mac=no comment="Default bridge" name=bridge port-cost-mode=short

/interface ethernet
set [ find default-name=ether1 ] comment="Living room AP" name=ETH1
set [ find default-name=ether5 ] comment="Office AP" name=ETH5 poe-out=off

/interface vlan
add interface=bridge name=vlan200 vlan-id=200

/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN

/ip pool
add name=dhcp_pool200-HASS ranges=192.168.200.30-192.168.200.100
add name=dhcp_pool-LAN ranges=192.168.0.100-192.168.0.240

/ip dhcp-server
add add-arp=yes address-pool=dhcp_pool200-HASS interface=vlan200 lease-time=1h name="dhcp 200-HASS"
add add-arp=yes address-pool=dhcp_pool-LAN interface=bridge lease-time=1h name="dhcp LAN"

/interface bridge port
add bridge=bridge ingress-filtering=no interface=ETH4 internal-path-cost=10 path-cost=10
add bridge=bridge ingress-filtering=no interface=ETH5 internal-path-cost=10 path-cost=10
add bridge=bridge ingress-filtering=no interface=ETH2 internal-path-cost=10 path-cost=10
add bridge=bridge ingress-filtering=no interface=ETH3 internal-path-cost=10 path-cost=10
add bridge=bridge ingress-filtering=no interface=ETH1 internal-path-cost=10 path-cost=10 trusted=yes

/interface bridge vlan
add bridge=bridge vlan-ids=200

/interface wireless cap
set bridge=bridge caps-man-addresses=192.168.0.1

/ip address
add address=192.168.0.1/24 interface=bridge network=192.168.0.0
add address=192.168.200.1/24 interface=vlan200 network=192.168.200.0
add address=192.168.211.1/29 interface=lo network=192.168.211.0

/ip dhcp-server lease
add address=192.168.0.31 address-lists="MikroTik AP,MikroTik Devices" client-id= mac-address= server="dhcp LAN"
add address=192.168.0.32 address-lists="MikroTik AP,MikroTik Devices" client-id= mac-address= server="dhcp LAN"

/ip dhcp-server network
add address=192.168.0.0/24 comment=defconf dns-server=192.168.0.7 domain= gateway=192.168.0.1 netmask=24
add address=192.168.200.0/24 dns-server=192.168.0.7 domain= gateway=192.168.200.1 netmask=24

Related Audience configuration (the one with Router OS 7)

# RouterOS 7.20.1

/interface bridge
add name=bridge port-cost-mode=short vlan-filtering=yes

/interface vlan
add interface=bridge name=vlan200 vlan-id=200

/interface wifi channel
add band=2ghz-n disabled=no frequency=2417 name=2GHz skip-dfs-channels=all width=20mhz

/interface wifi datapath
add bridge=bridge disabled=no interface-list=dynamic name=Default vlan-id=200

/interface wifi security
add disabled=no name=Default

/interface wifi configuration
add channel=2GHz country=Greece datapath=Default disabled=no distance=1 mode=ap name="IoT2.4GHz" security=Default ssid=IoT2.4

/interface wifi
# vlan-id configured, but interface does not support assigning vlans
set [ find default-name=wifi1 ] channel.frequency=2417 configuration="IoT2.4GHz" configuration.mode=ap

/interface bridge port
add bridge=bridge ingress-filtering=no interface=ether1 internal-path-cost=10 path-cost=10 trusted=yes
add bridge=bridge ingress-filtering=no interface=wifi1 internal-path-cost=10 path-cost=10 trusted=yes

/interface bridge vlan
add bridge=bridge tagged=bridge,ether1 vlan-ids=200

/ip dhcp-client
# DHCP client can not run on slave or passthrough interface!
add add-default-route=no default-route-tables=main interface=ether1

Thanks in advance

wifi-qcom-ac does not support setting VLAN info via datapath.

I think you are confused with your definition of Mesh.
Mesh as Mikrotik uses it, means using a wireless backhaul to connect different APs together.
Some devices have a 3th radio only for that purpose. You don't need wires then from AP to router/switch.
But since you state you do not have wireless coverage everywhere, using mesh could become a problem.

What I think you want is full wifi coverage for client devices using a single SSID across access points. Correct ?
And roaming between access points when clients move around. Correct ?
All access points are connected to Hex S using ethernet cable. Yes ?
All devices are on ROS7 and APs have wifi-qcom or wifi-qcom-ac drivers.
That's when you use capsman.

See here for Help pages with instructions how to set up.
(first generic, then the specifics for wifi-qcom-ac)