debcrafters-packages team mailing list archive

[Nick Rosbrook <2117180@xxxxxxxxxxxxxxxxxx>]

Hello Mitchell, or anyone else affected,

Accepted wpa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu2.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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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 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