Verified on Plucky:

❯ apt-cache policy wpasupplicant
wpasupplicant:
  Installed: 2:2.10-24ubuntu0.1
  Candidate: 2:2.10-24ubuntu0.1
  Version table:
 *** 2:2.10-24ubuntu0.1 100
        100 http://us.archive.ubuntu.com/ubuntu plucky-proposed/main amd64 
Packages
        100 /var/lib/dpkg/status
     2:2.10-24 500
        500 http://us.archive.ubuntu.com/ubuntu plucky/main amd64 Packages      
                                                                                
                                                                                
           ❯ sudo wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <[email protected]> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlp4s0'

Interactive mode

<3>CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=156000
> get bss_max_count
1000             


and on Noble:
$ sudo wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <[email protected]> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlP9s9'

Interactive mode

> get bss_max_count
1000
mitchell@device:~$ apt-cache policy wpasupplicant 
wpasupplicant:
  Installed: 2:2.10-21ubuntu0.3
  Candidate: 2:2.11-0ubuntu4~24.04.1
  Version table:
 *** 2:2.10-21ubuntu0.3 100
        100 http://ports.ubuntu.com/ubuntu-ports noble-proposed/main arm64 
Packages
        100 /var/lib/dpkg/status
     2:2.10-21ubuntu0.2 500
        500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 
Packages
        500 http://ports.ubuntu.com/ubuntu-ports noble-security/main arm64 
Packages
     2:2.10-21build4 500
        500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages


and on Jammy:
maugustinpersonal@Computito:~$ apt-cache policy wpasupplicant
wpasupplicant:
  Installed: 2:2.10-6ubuntu2.3
  Candidate: 2:2.10-6ubuntu2.3
  Version table:
 *** 2:2.10-6ubuntu2.3 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
        100 /var/lib/dpkg/status
     2:2.10-6ubuntu2.2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     2:2.10-6 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
maugustinpersonal@Computito:~$ sudo wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <[email protected]> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlp2s0'

Interactive mode

> get  bss_max_count
1000

The desired functional impact was also confirmed (all APs in range
appeared in the congested area), and we have not observed any unexpected
functional issues since deploying this change in QA so far.

** Tags removed: verification-needed verification-needed-jammy 
verification-needed-noble verification-needed-plucky
** Tags added: verification-done verification-done-jammy 
verification-done-noble verification-done-plucky

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2117180

Title:
  wpa_supplicant DEFAULT_BSS_MAX_COUNT is too low for populated areas

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Committed
Status in wpa source package in Noble:
  Fix Committed
Status in wpa source package in Plucky:
  Fix Committed

Bug description:
  SRU Justification:

  [ Impact ]

  In densely-populated areas with more than 200 Wi-Fi APs,
  wpa_supplicant's default BSS_MAX_COUNT of 200 causes some nearby wi-fi
  APs to only appear inconsistently.

  In areas with more APs, setting a higher bss_max_count of 500 via
  wpa_cli was sufficient to resolve this issue. Since such dense areas
  are now common, it may be appropriate to raise the default to 500 or
  1000.

  [ Test Plan ]

  Run an nmcli scan in an area with 500+ APs, with and without the
  described wpa_supplicant change. Confirm that the change results in
  all expected APs being present.

  [ Fix ]

  Bump the DEFAULT_BSS_MAX_COUNT to 1000

  [ Where problems could occur ]

  It's conceivable that there could be differences in time required to
  scan / enumerate more APs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2117180/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to