Two packages: wireless and wifi
wireless (old) |
wifi (since RouterOS 7.13) |
|
|---|---|---|
| Menu | /interface wireless |
/interface wifi |
| Drivers | all older models | wifi-qcom — Qualcomm Wi-Fi 6 and newer; wifi-qcom-ac — Wi-Fi 5 on ARM |
| Models | hAP ac lite, hAP lite, cAP ac on MIPS | hAP ax², ax³, ax S, cAP ax, wAP ax, Chateau ax; optionally hAP ac², ac³, cAP ac |
| WPA3, OWE, 802.11w | no | yes |
| 802.11r/k/v roaming | no | yes |
| CAPsMAN | the old one, /caps-man |
the new one, /interface wifi capsman |
| MikroTik’s own | Nstreme, Nv2 — for radio links over kilometres | none |
Wi-Fi 6 models have no choice — only wifi. The hAP ac² and ac³ ship with wireless; moving to wifi-qcom-ac brings
WPA3 and roaming but takes more memory, and VLAN tagging from the access point (datapath.vlan-id) doesn’t work on ac
chips. Wi-Fi on the hAP be lite and hAP ax S runs on MediaTek chips with the wifi-mediatek package; the hAP ax², ax³
and cAP ax use wifi-qcom, the hAP be³ Media wifi-qcom-be. They all share one menu — /interface wifi.
What the wifi package does
Radio settings are grouped into sections; you can set them right on the interface or as a shared profile:
/interface wifi print detail
# name="wifi1" default-name="wifi1"
# channel.band=5ghz-ax .width=20/40/80mhz .skip-dfs-channels=10min-cac
# configuration.mode=ap .ssid="MikroTik-1A2B3C" .country=Latvia
# security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes
That’s roughly the hAP ax² factory config. The sections:
channel— band, width, frequency, DFS.skip-dfs-channels=10min-cacmeans don’t pick channels with a 10-minute radar wait.configuration— mode (ap,station), network name, country. The country sets the allowed channels and power; set the one where the router stands —Latviain the examples below.security—wpa2-psk,wpa3-psk(mixed mode), the password,ft=yesfor 802.11r roaming.datapath— where client traffic goes:bridge,vlan-id,client-isolation=yes(clients of one network can’t see each other — for guests).steering— 802.11k (rrm) and 802.11v (wnm) hints to clients, on by default.
A second network on the same radio is a virtual interface: add master-interface=wifi1 name=wifi1-guest, with its own
name, password and bridge (Guest network on MikroTik).
Several access points: CAPsMAN
The router is the manager, the access points are CAPs. Network settings (name, password, VLAN) are set on the router, and access points pick them up themselves. The router commands are checked on 7.24, the access point ones aren’t1:
# on the router
/interface wifi capsman set enabled=yes ca-certificate=auto interfaces=bridge
/interface wifi configuration add name=home ssid=home country=Latvia \
security.authentication-types=wpa2-psk,wpa3-psk security.passphrase="…" \
security.ft=yes
/interface wifi provisioning add action=create-dynamic-enabled \
master-configuration=home supported-bands=5ghz-ax
/interface wifi provisioning add action=create-dynamic-enabled \
master-configuration=home supported-bands=2ghz-ax
# on each access point
/interface wifi cap set enabled=yes discovery-interfaces=bridge
/interface wifi set wifi1,wifi2 configuration.manager=capsman-or-local
The easiest way to put an access point into CAP mode is the button: hold reset while powering on until the LED starts
flashing, then about 5 seconds more until it’s steady. Without the button: /system reset-configuration caps-mode=yes.
Access points connect to the router by cable, which also carries PoE power.
Roaming: what the router does and what the phone does
The phone always decides when to switch access points. The network can only make it easier:
| Standard | What it does | In RouterOS |
|---|---|---|
| 802.11r | the key is ready in advance: a switch takes tens of milliseconds, a call doesn’t drop | security.ft=yes, the same network name and password on every access point |
| 802.11k | the access point gives the phone a list of neighbouring access points | steering.rrm=yes, by default |
| 802.11v | the access point asks the phone to move when the signal is weak | steering.wnm=yes, by default |
Old devices stumble over 802.11r: 2.4 GHz smart plugs and some printers stop connecting to a network with ft=yes.
Give them a separate network without roaming.
Where MikroTik falls behind consumer routers
- Streams and width. The hAP ax² and ax³ have two streams each, up to 1200 Mbit/s on 5 GHz on paper, width up to 80 MHz. Consumer flagships give 4 streams and 160 MHz. For one phone the difference is small; for an apartment with dozens of devices and walls, it shows.
- Wi-Fi 7. The hAP be lite (BE3600) and hAP be³ Media (BE9300, “coming soon”) are the first Wi-Fi 7 models, in 2026. ASUS, TP-Link and UniFi have sold Wi-Fi 7 since 2024.
- Wireless mesh. MikroTik access points are connected by cable. A wireless link between access points is set up
by hand in
station-bridgemode and halves the speed — there’s no ready mesh from an app like Deco’s. - Channel selection. Auto channel works at startup; cloud-backed consumer routers move channels overnight with the neighbours in mind. Here, with a bad radio environment, you set the channel yourself.
Where it’s good
- One network for the whole home. CAPsMAN and 802.11r give what people buy UniFi for: settings in one place, switching between access points without drops.
- Guest and service networks with client isolation, their own DHCP and firewall rules — as many as you need.
- You see the airwaves and the clients.
registration-tableshows each client’s signal level, rate and connection time;/interface wifi scan wifi1lists neighbouring networks and their channels. - Access points for ceilings and outdoors. The cAP ax and wAP ax run on PoE and are managed from the router.
If it doesn’t work
The 5 GHz network disappears for a minute, or even 10, and comes back on another channel
- Cause
- The access point was on a DFS channel (52–144) and heard radar — or thought it did. By the rules it must leave the channel and stay off it for up to 30 minutes; on a new DFS channel it listens for a minute before starting, 10 minutes on 120–128.
- Fix
- Pick a non-DFS channel 36–48:
/interface wifi set wifi1 channel.frequency=5180-5240:20— a range with a 20 MHz step. Or keepskip-dfs-channels=10min-cacfrom the default config — then the access point at least avoids the channels with a 10-minute wait.
Next to the router, 5 GHz gives 200 Mbit/s instead of 600–900
- Cause
- The channel is 20 or 40 MHz wide instead of 80, or the phone joined 2.4 GHz: one network name covers both bands.
- Fix
/interface wifi registration-table printshows which interface the client is on and at what rate (tx-rate). Check the width in/interface wifi print detail, thechannel.widthline.
An old laptop or a smart plug can’t see the network after the switch to WPA3
- Cause
- The device only does WPA2, and
authentication-typeshas justwpa3-psk. 2.4 GHz smart plugs may also lack 802.11r support. - Fix
- Set
wpa2-psk,wpa3-psk— mixed mode. For plugs, a separate 2.4 GHz network withoutft=yes(Guest network on MikroTik).
After moving to CAPsMAN, the access point won’t connect to the router
- Cause
- The old CAPsMAN (
/caps-man) manages access points with the oldwirelesspackage; the new one (/interface wifi capsman) only those with thewifipackage. They can’t be mixed. - Fix
- Use the same package on the router and the access points:
wifi-qcomfor ax,wifi-qcom-acfor ac on ARM. On the access point:/interface wifi cap set enabled=yesandconfiguration.manager=capsman-or-localon the radios.
The phone clings to a far access point though another is right there
- Cause
- The phone decides when to switch. 802.11k and 802.11v only hint where to go; if the far access point transmits at high power, the phone sees its signal as good enough.
- Fix
- Lower access point power (
channel.tx-power) so coverage areas overlap less, and check that 802.11r is on (security.ft=yes) on every access point with the same network name.
Not verified yet
- the access point commands —
/interface wifi capandconfiguration.manageron a cAP ax with 7.24 ↑