Virtual Wi-Fi on new Wi-Fi menu

RouterOS Wireless Networking
1

i am running a cAP XL AC. i upgraded the wireless driver to the new wifi-qcom-ac driver package. that part is fine.

my question is, on the new qcom-ac package, how do i do multiple ssid’s on different vlans?

my understanding is with the mikrotik vlan situation is:

  1. vlan-aware bridge (filtering enabled, pvid 1)
  2. pvid 1 on wifi1 interface
  3. pvid50 on new virtual wi-fi interface with ssid/password config
  4. add vlan50 to bridge vlan table, tagging port1, wifi1

that should be it, no? somehow, it doesn’t work. if i back it off one step though, it works. eg:

  1. vlan-aware bridge (filtering enabled, pvid 1)
  2. pvid50 on wifi1 interface, add ssid/password config
  3. add vlan50 to bridge vlan table, tagging ether1

so why can’t i do it with a virtual wi-fi? somehow, it doesn’t start broadcasting and remains “inactive”

2

/export file=anynameyouwish (minus router serial number, any public WANIP information, keys)

3

this is the working config:

# software id = ZHWP-91EG
#
# model = RBcAPGi-5acD2nD
# serial number = sdefgwe45
/interface bridge
add frame-types=admit-only-vlan-tagged name=bridge1 port-cost-mode=short \
    vlan-filtering=yes
/interface ethernet
set [ find default-name=ether2 ] disabled=yes
/interface wifi
set [ find default-name=wifi1 ] channel.width=20/40mhz-Ce \
    configuration.country="United States" .mode=ap .ssid=whatever .tx-power=\
    40 disabled=no security.authentication-types=wpa2-psk,wpa3-psk
# SSID not set
set [ find default-name=wifi2 ] configuration.mode=ap disabled=no
/interface vlan
add interface=bridge1 name=MGMT vlan-id=2
/interface lte apn
set [ find default=yes ] ip-type=ipv4 use-network-apn=no
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disabled=no name=sec1
/interface wifi
add configuration.mode=ap .ssid=whatever datapath=*1 mac-address=\
    F6:1E:57:7C:58:22 master-interface=wifi1 name=whatever \
    security.authentication-types=wpa2-psk,wpa3-psk
/interface bridge port
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=ether1 \
    internal-path-cost=10 path-cost=10
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \
    interface=wifi1 pvid=3
/ip firewall connection tracking
set udp-timeout=10s
/ip settings
set max-neighbor-entries=8192
/ipv6 settings
set disable-ipv6=yes max-neighbor-entries=8192
/interface bridge vlan
add bridge=bridge1 tagged=ether1 vlan-ids=2,3
/interface ovpn-server server
add auth=sha1,md5 mac-address=FE:00:99:CD:0F:20 name=ovpn-server1
/ip address
add address=10.10.1.2/27 interface=MGMT network=10.10.1.0
/ip dns
set servers=8.8.8.8
/ip hotspot profile
set [ find default=yes ] html-directory=hotspot
/ip ipsec profile
set [ find default=yes ] dpd-interval=2m dpd-maximum-failures=5
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=10.10.1.1 routing-table=main \
    suppress-hw-offload=no
/routing bfd configuration
add disabled=no interfaces=all min-rx=200ms min-tx=200ms multiplier=5
/system clock
set time-zone-name=America/Chicago
/tool sniffer
set filter-interface=all filter-ip-protocol=icmp
4

Wifi-qcom and wifi-qcom-ac drivers are ALMOST the same (explicit emphasis on “almost”).
VLAN handling is one of those important differences.

For qcom-ac drivers you need to set VLANs on the interfaces and bridge. Can’t be done the same way as for AX devices.

5

ok I have no issues getting vlans to work using interfaces and bridges in the classic mikrotik way. my issue is, getting vlans to work using brides and virtual interfaces, e.g. creating an additional ssid on a wi-fi interface. this is just a standalone ap, no capsman.

6

Nobody mentioned capsman ?

You make your slave wifi interface.
It will appear as an added interface.
Add it to bridge as any other interface.

From there, the VLAN stuff is like for any other interface.

7

only the mt docs :slight_smile:

does the master interface become a “truck port” in that case? or does it remain a regular access port alongside the virtual interface?

8

Surely you mean “trunk” (as in: interface carrying multiple VLANs)

The master interface is only used to carry the subsequent slave interfaces on a physical level.

On bridge level, master and slave (in this context) are identical types of interfaces.
The only thing you can not do on a slave interface is deviate from the physical properties as defined by master interface (e.g. frequency).
But for VLANs etc, both interfaces are handled as any other interface and can be set up completely different from each other.

9

lol. yes. i don’t usually respond from mobile :slight_smile:

alright. thank you for that. i will head back to the lab and try again. i am certain i tried every combination of everything yesterday, including trying to cast spells