OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium common DISPUTE

Pin the Wi-Fi band when NetworkManager thrashes onto 6 GHz or sticks to 2.4 GHz

omarchyarchendeavouroscachyosmanjaronetworkmanagerwpa_supplicantmediatekintellaptop
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Issue #7311 (open) supports the 6 GHz thrash symptom: the freq=6135 association loop, DEAUTH_LEAVING with locally_generated=1, the gateway RTT figures (43 ms average, 135 ms max, 2.7 ms after the workaround) and the band a workaround on mt7921e. Its comment adds the AX210 report with iwlwifi: Unhandled alg: 0x707 and SAE/FT-SAE on 6 GHz. Issue #11812 (open, 4.0.3-1, MT7902/mt7921e) supports the stuck-on-2.4 GHz case (17.2 Mbit/s, about 565 ms ping). /usr/share/omarchy/bin/omarchy-network-band on 4.0.4-1 accepts auto, 2.4, 5 and 6, maps 5 to NM band a, prints band, available and selected with no argument, and reverts the previous band if nmcli connection up fails, as the record says. The omarchy dispatcher routes omarchy network band to that binary, and iw (6.17-1) is installed. The nm-settings-nmcli(5) man page for NetworkManager 1.58.1 says a will not associate on 2.4 GHz or 6 GHz. NetworkManager's nm-supplicant-config.c returns early from bgscan setup when a BSSID is locked, which confirms the claim that a BSSID pin disables background scanning. The verify frequency range matches the script's 4900 to 5925 MHz boundary. Nothing was changed on this machine.

RISK

A band pin is stored in the profile and follows it everywhere. On a network that has no 5 GHz radio, a pinned profile will not connect until you run omarchy network band auto.

Symptom

Two complaints with one fix. (1) Since moving to Omarchy 4 (NetworkManager and wpa_supplicant), Wi-Fi feels laggy and calls stutter, yet speed tests look fine. Gateway ping jumps from 2 ms to 40 to 135 ms. The journal loops through Trying to associate with ... freq=6135 MHz, deauthenticating ... by local choice (Reason: 3=DEAUTH_LEAVING), CTRL-EVENT-DISCONNECTED ... locally_generated=1, and then falls back to 5 GHz. On Intel AX210 it can also log iwlwifi: Unhandled alg: 0x707. (2) On a fresh install the laptop joins the 2.4 GHz radio of a dual-band router (17 Mbit/s, 500 ms ping) even though the same SSID is on 5 GHz.

Cause

With one SSID broadcast on 2.4, 5 and 6 GHz, wpa_supplicant's BSS selection picks whichever radio looks best at scan time. A strong but marginal 6 GHz signal, or a 6 GHz radio that needs SAE or FT-SAE the client handles badly, makes it roam there, fail to hold the association and fall back, over and over. On some cards it can also settle on 2.4 GHz. iwd, which Omarchy 3 used, did not show this on the same hardware, which is why it appears as a Quattro regression. It is upstream supplicant behaviour, reported on MediaTek mt7921e and Intel AX210.

Fix

Omarchy 4 has a helper that pins the band on the active profile, and it reverts on its own if the band cannot connect:


omarchy network band            # shows current band, available bands, selected pin
omarchy network band 5          # pin to 5 GHz (same as: omarchy-network-band 5)
omarchy network band auto       # remove the pin

Plain Arch, or to do it by hand:


nmcli -f NAME,DEVICE connection show --active
nmcli connection modify 'MyWifi' 802-11-wireless.band a
nmcli connection up 'MyWifi'
# undo:
nmcli connection modify 'MyWifi' 802-11-wireless.band ''

band a keeps the connection on 5 GHz and away from both 2.4 and 6 GHz. Pinning the band is better than pinning a BSSID with 802-11-wireless.bssid, which disables background scanning and roaming between access points.

Verify

iw dev <iface> link shows freq: between 4900 and 5925. journalctl -b -u wpa_supplicant has no new freq=6 association attempts. ping -c 50 <gateway> shows low, steady times.

Sources

wifi-wrong-band-6ghz-thrash-or-stuck-2ghz