Report the highest-band link and MLO state in network band and status - #9809
Open
SDCVO wants to merge 1 commit into
Open
Report the highest-band link and MLO state in network band and status#9809SDCVO wants to merge 1 commit into
SDCVO wants to merge 1 commit into
Conversation
SDCVO
marked this pull request as ready for review
September 2, 2026 12:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
On a Wi-Fi 7 MLO (Multi-Link Operation) connection, the AP exposes one radio link per band under a single SSID, and
iw dev <dev> linkprints each link with its ownfreq:line — Link 0 (typically 2.4 GHz) first:omarchy-network-bandandomarchy-network-statusextracted the firstfreq:line, so a 2.4+5 GHz association was always reported as 2.4GHZ in the network panel, even though the 5 GHz link carries the traffic and is the BSSID NetworkManager reports as in-use. Pinning the band "worked" only because it forced a single-band association.Fix
bin/omarchy-network-band/bin/omarchy-network-status— select the highest-band link's frequency instead of the first. Non-MLO output is unchanged (a singlefreq:yields the same value).bin/omarchy-network-band— emit a newmlo\t0|1line, detected by countingfreq:links, so the shell can tell split-link associations apart.shell/plugins/panels/network/Model.js—parseBandStatusreads the flag;bandSectionTitleappends· MLObeside the live band.shell/plugins/panels/network/Panel.qml— newbandMloproperty wired into the band header.The panel's band header now reads:
and stays plain (
WI-FI BAND: 5GHZ,WI-FI BAND: 2.4GHZ) for single-link connections.Tests
test/shell.d/network-band-test.sh(stubbediw/nmcli):band 5,mlo 1band 6,mlo 1mlo 0test/shell.d/network-test.sh— coverage for the MLO header variants (live, plain, pinned) and themlofield inparseBandStatus../test/allpasses apart from the 3 pre-existingomarchy-pkgscheckout failures on this machine (environment-related, unrelated to this change).The
· MLOsuffix intentionally only appears under Automatic (when the header carries the live band); once a band is pinned the pills show instead and the header stays plain — matching the existing design.