debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #04021
[Bug 2116940] Re: Nmcli incorrectly reports Wi-Fi channel as 0 for 6 GHz AP
There is an upstream PR about it:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2110
The review is fairly advanced, however it's a bit stalled. The author
disappeared for a few months, got back alive a few weeks ago, and it's
stalled again. Also, the PR is broader than just this channel thing.
I will help the upstream PR move forward and, in parallel, I will
propose a smaller subset of it in a patch that can be SRU'd.
--
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2116940
Title:
Nmcli incorrectly reports Wi-Fi channel as 0 for 6 GHz AP
Status in network-manager package in Ubuntu:
New
Status in network-manager source package in Noble:
New
Status in network-manager source package in Plucky:
New
Status in network-manager source package in Questing:
New
Bug description:
We are observing that when connecting to a 6 GHz Wi-Fi access point
(channel 169), the nmcli tool incorrectly reports the channel as 0,
while other tools like iw dev and wpa_cli reflect the correct value.
The issue affects the accuracy of WiFi scanning, potentially leading
to incorrect channel information and difficulties in using the WiFi
network.
Repro steps:
- Power on the target
- Turn on the wifi 6GHz band network (Using WiFi7 TP BE19000)
- Set the region to US
$ sudo iw reg set US
- Scan the network using the cmd:
$ nmcli dev wifi list
Expected Result:
The channel set in the router should display in scan list
Additional comments:
After connecting to 6G WiFi, and executed the command
$ sudo iw dev
We are able to see the channel as 169,
and verified that in router page 6G AP channel is set to 169 itself.
However, when scanning 6G AP using nmcli, the channel is displaying as 0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2116940/+subscriptions
References