debcrafters-packages team mailing list archive

[Julian Andres Klode <2116940@xxxxxxxxxxxxxxxxxx>]

Hello Antoine, or anyone else affected,

Accepted network-manager into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.46.0-1ubuntu2.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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:
  Fix Released
Status in network-manager source package in Noble:
  Fix Committed
Status in network-manager source package in Plucky:
  Fix Committed
Status in network-manager source package in Questing:
  Fix Released

Bug description:
  SRU Justification:

  [ Impact ]

   * All systems compatible with wifi 6E (6 ghz endpoint) are currently
  reporting an incorrect channel when using the `nmcli` tool to scan the
  network.

   * This patch provides minimal changes to address this problem. It
  adds the <frequency-channel> pairs that are missing in the code, and
  handles the few case where hard-coded exits where implemented for
  frequencies > 5.9 ghz.

  
  [ Test Plan ]

   1. Run `nmcli device wifi list` without / with the patch. See that
  the channel is not zero anymore

   2. Run the Wireless Network certification suite from Checkbox, that will 
      * Connect and disconnect to all kind of wifi
      * Scan the network

      All the tests should be successfull.

      wireless/wireless_scanning_interface                  
      wireless/wireless_connection_wpa_bg_nm_interface      
      wireless/wireless_connection_open_bg_nm_interface     
      wireless/wireless_connection_wpa_n_nm_interface       
      wireless/wireless_connection_open_n_nm_interface      
      wireless/wireless_connection_wpa_ac_nm_interface      
      wireless/wireless_connection_open_ac_nm_interface     
      wireless/wireless_connection_wpa_ax_nm_interface      
      wireless/wireless_connection_wpa3_ax_nm_interface     
      wireless/wireless_connection_open_ax_nm_interface     
      wireless/wireless_connection_wpa_be_nm_interface      
      wireless/wireless_connection_wpa3_be_nm_interface     
      wireless/wireless_connection_open_be_nm_interface     

  
  [ Where problems could occur ]

   * Some function where existing or returning (0,0) when using wifi 6E
  before this patch. I made sure that it would not cause an unexpected
  behavior later.

  
  [ Other Info ]

   * The patch is a subset of an upstream, unmerged, PR: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2110
  The above upstream PR contains other changes that are not relevant for a SRU (refactoring, for example). It went through several rounds of review already but is a bit stalled lately. Since one of our partners (nvidia) asks for a fix, I am proposing this patch and will help the PR move forward in parallel. Once the PR is merged upstream, the patch can be dropped from Questing.


  
  original 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