This bug was fixed in the package wpa - 2:2.10-21ubuntu0.3 --------------- wpa (2:2.10-21ubuntu0.3) noble; urgency=medium
* Bump DEFAULT_BSS_MAX_COUNT to 1000 (LP: #2117180) -- Mitchell Augustin <[email protected]> Mon, 21 Jul 2025 18:13:31 -0500 ** Changed in: wpa (Ubuntu Noble) Status: Fix Committed => Fix Released -- 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 Released Status in wpa source package in Plucky: Fix Released 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
