UniFi Advanced Wireless Settings: What Each One Does

Switch a UniFi SSID from Advanced: Auto to Advanced: Manual and a second tier of the network appears: roaming behaviour, power save, multicast handling, minimum data rates, isolation, DFS. Most of it is off by default, and most of it is off by default for a defensible reason.

People go looking anyway because of a symptom — a phone that clings to the far AP, a doorbell that drops every night, a speaker that will not appear in the app. This page is the reference for what each setting changes, what it costs, and which symptom justifies touching it.

One rule before any of it. Change one setting at a time, write down what it was, and give it a day. Wireless faults are intermittent and client-specific, and three simultaneous changes produce a network nobody can attribute behaviour to. If the network already misbehaves, work the ordered slow-Wi-Fi troubleshooting method first — most complaints resolve to placement, channel width, or the WAN, not to a toggle.

Roaming: the four settings that decide where clients land

Clients choose their own access point. Nothing in UniFi can force a device to roam. These settings make roaming easier and make staying put less attractive.

Band Steering — on by default. The AP nudges dual-band-capable clients off 2.4 GHz toward 5 GHz using BSS transition frames, at the standardised protocol level rather than the old AP-level trickery. Leave it on. Turn it off only if a specific client refuses to associate or flaps between bands, and expect that client to be an older IoT device.

BSS Transition (802.11v) — on by default. Lets the AP tell a client there is a better AP nearby and identify it. Purely advisory, clients are free to ignore it, but it costs nothing and helps well-behaved devices. Leave it on in any multi-AP site.

Fast Roaming (802.11r) — off by default. Speeds up the security key exchange when a client moves between APs, cutting the handover gap. Worth enabling when real-time traffic matters: Wi-Fi calling, VoIP handsets, video meetings on a laptop carried between rooms. The catch is client support — a handful of older devices handle 802.11r badly and fail to associate at all, so check the client list afterwards for anything that stopped connecting.

Minimum RSSI — off by default. This is the blunt instrument. It sets a signal floor, and when a client’s signal drops below it the AP disconnects the client so it has to reassociate — hopefully with a nearer AP. Ubiquiti’s own minimum RSSI guidance is explicit that the purpose is to break the “sticky client” pattern where a device hangs on to a distant AP at a terrible rate.

Two cautions matter more than the setting itself. Set too aggressively it creates disconnections rather than roams — around -70 dBm is a common starting point, while -60 dBm in a two-AP house evicts clients from perfectly usable coverage. And it cannot fix a coverage gap: a device at -78 dBm with no closer AP just reconnects to the same one. The fix there is another access point, planned with proper placement and channel discipline. Reach for Minimum RSSI last, after placement and transmit power are right.

Power save: UAPSD and DTIM

UAPSD (Unscheduled Automatic Power Save Delivery) — off by default. It lets a client keep its radio asleep longer and pull buffered frames on its own schedule, which helps battery life on phones and battery-powered sensors. It ships off because implementation quality varies wildly across clients: older devices and cheap IoT hardware sometimes miss their wake windows, which surfaces as random disconnections or high latency. Enable it on the SSID that carries phones and laptops, leave it off on the IoT SSID, and if a device starts dropping the next day you have your answer.

802.11 DTIM Period — leave on auto. DTIM controls how often the AP announces buffered broadcast and multicast traffic to sleeping clients; UniFi defaults to 1 on 2.4 GHz and 3 on 5 GHz. Raising it saves a little more client battery at the cost of multicast latency, and lowering it does the reverse. The gain either way is small and the failure modes are not.

Airtime: data rates, multicast, and ARP

Everything in this group is about not wasting airtime, which is the only truly finite resource in a wireless network.

Minimum Data Rate Control — all rates allowed by default. The setting defines the slowest rate a client is permitted to use on the SSID. It matters because a client transmitting at 1 Mbps occupies the channel roughly fifty times longer than the same frame at 54 Mbps, and while it does, nothing else on that channel transmits. One distant device on legacy rates degrades everyone.

Raising the floor — disabling the old 1, 2, 5.5 and 11 Mbps rates on 2.4 GHz — reclaims that airtime and encourages distant clients to roam sooner. It also hard-limits your coverage radius, because a client that cannot sustain the minimum rate cannot associate at all. That is the intended behaviour in a dense office with many APs and a hostile one in a house with two. Leave it alone in a home; in a high-density site with overlapping coverage, raising the 2.4 GHz floor is one of the highest-value changes available.

Multicast Enhancement (IGMPv3) — off by default. Converts multicast frames to unicast where the AP can identify the recipients, which saves airtime and often makes discovery protocols behave. Worth trying when Chromecast, AirPlay or a networked printer appear intermittently, though it is not guaranteed to help.

Multicast and Broadcast Control — off by default. Blocks multicast and broadcast on the SSID except for devices you explicitly allow. Powerful on guest and high-density networks where broadcast chatter is pure overhead, but it breaks discovery for anything you forget to allow, so treat the exception list as part of the configuration.

Proxy ARP — off by default. The AP answers ARP requests on behalf of its associated clients using unicast frames instead of flooding a broadcast across the wireless segment. On a busy network that is a meaningful reduction in background noise and it cuts the wake-ups broadcast traffic inflicts on sleeping devices. Worth enabling on high-density sites, unnecessary on a two-AP home network. Note that ARP and neighbour-cache timing is a gateway and switch concern as much as a wireless one, and the segmentation model matters — see VLAN segmentation for IoT, guest, and trusted.

Isolation and security

Client Device Isolation — off by default. Stops clients on the same SSID talking to each other. Correct on guest and IoT networks, disruptive on a trusted one where it breaks casting, printing, and file sharing. It is Layer 2 protection per SSID and complements, rather than replaces, firewall rules between VLANs; the guest network and captive portal guide covers what guest isolation does and does not contain.

Hide Wi-Fi Name — off by default, and it should stay there. Hiding the SSID keeps the name out of beacons, but it still travels in plain association traffic and any scanner recovers it in seconds. Meanwhile clients configured for a hidden network probe for it constantly, broadcasting the name from every device you own. It buys nothing and costs something.

PMF (Protected Management Frames) — required with WPA3, optional with WPA2. PMF stops management frames being forged, closing off trivial deauthentication attacks. On 6 GHz it is not optional: the band mandates WPA3 or OWE with PMF, which is why legacy IoT devices cannot join a 6 GHz-enabled SSID and why Wi-Fi 6E access points force a separate IoT SSID.

Group Rekey Interval — 3600 seconds by default. How often the group key protecting broadcast and multicast traffic rotates. Shortening it is a marginal security gain and a reliable way to introduce dropouts on clients with sloppy rekey handling. Leave it.

Radio settings: width, power, and DFS

These live on the AP rather than the SSID, and they move performance far more than anything above.

Channel width. Wider is not better: a wider channel is a bigger target for interference and leaves fewer non-overlapping channels for neighbouring APs. Sensible defaults are 20 MHz on 2.4 GHz always, 40 to 80 MHz on 5 GHz, 80 to 160 MHz on 6 GHz.

Transmit power. The instinct is to turn it up. In a multi-AP site that is exactly wrong, because it extends the range at which clients stay stuck to a distant AP without improving what those clients can hear coming back. A common adjustment is to run 2.4 GHz around 6 dBm below 5 GHz, since 2.4 GHz already travels further and otherwise pulls clients onto the slower band.

DFS channels. Large parts of the 5 GHz band are shared with radar and gated by Dynamic Frequency Selection. DFS channels are far less congested because most consumer routers avoid them, but an AP that detects radar must vacate immediately, and the availability check before it can return runs from one minute up to ten on the higher sub-bands in some regulatory domains. All supported 5 GHz UniFi access points can use DFS channels.

Two practical notes. Some Windows and Android clients do not see certain DFS channels at all and will simply not find the network there. And “zero wait DFS”, where the AP monitors a backup channel so it can switch instantly instead of going quiet, is a per-model capability rather than a UniFi-wide feature; check the specific access point’s specifications before planning around it. If DFS is causing nightly outages, pin the AP to a non-DFS channel and accept the congestion rather than hunting for a cleaner DFS channel.

A sane starting profile

For a typical home or small office running UniFi:

Setting	Trusted SSID	IoT SSID	Guest SSID
Band steering	On	Off	On
BSS transition	On	On	On
Fast roaming (802.11r)	On	Off	Off
Minimum RSSI	Off	Off	Off
UAPSD	On	Off	Off
Client device isolation	Off	On	On
Multicast and broadcast control	Off	Off	On
Proxy ARP	Off	Off	Off
Minimum data rate	Default	Default	Default
6 GHz enabled	Yes	No	No

That profile assumes coverage is already adequate. If it is not, none of these columns will save it — add an access point. The UniFi network planner will size AP count and PoE draw for a floor plan before you order anything.

Symptom to setting

Symptom	First thing to look at
Phone stays on the far AP at 1 bar	Transmit power, then AP placement, then Minimum RSSI
Calls drop while walking between rooms	Fast roaming (802.11r), BSS transition
Battery drain on phones	UAPSD on the trusted SSID
IoT device disconnects nightly	UAPSD off, band steering off, check DFS
Chromecast or printer not discovered	Multicast enhancement, client isolation, VLAN and mDNS rules
Whole 2.4 GHz band feels slow	Channel width 20 MHz, minimum data rate floor
Wi-Fi drops at the same time each evening	DFS radar events; move to a non-DFS channel
Everything is slow everywhere	Not these settings — start with the troubleshooting method

The honest summary

Almost every UniFi default is correct for almost every network. On a home network the changes worth making come down to a short list: fast roaming if calls matter, UAPSD on the SSID carrying phones, isolation on for guest and IoT, and channel widths that leave room for your neighbours. Dense sites add proxy ARP, broadcast control, and a raised 2.4 GHz data rate floor.

Everything else in the Manual panel exists for a specific problem you do not have yet, and changing it speculatively is how a working network becomes an intermittent one. When a setting does need to change, note the old value first, and keep a current controller backup so the configuration can be rolled back rather than reconstructed from memory.

Related across the network

• Keycloak Realms, Clients and Token Design Fundamentals — keycloakops.com
• OpenMediaVault Slow SMB Transfers: How to Fix — openmediavaultlab.com