"bad_bssid_counter_thresh" is an ini parameter to specify the threshold
after which the BSSID is in the avoid list should be moved to
deny list, assuming that the AP or the gateway with which the data
stall happened has not recovered, and now the STA got the NUD
failure again with the BSSID.
Currently, in driver sets max value for this ini param as 10.
But for some new requirement, this value is required to 100 as
user does not want any BSSID in reject list.
So, to enable this feature, increase the max value for this param
as 100.
Change-Id: I80e908c82ea74801bfcb04a9669cc4b4589f0dec
CRs-Fixed: 3382136
The kernel-doc script identified a few documentation issues in
components/denylist_mgr, so fix them.
Change-Id: I45fc8c6a637cebccf324dd44102b894fc84e7f2b
CRs-Fixed: 3361722
Allow roam invoke on bssid in monitor list but reject bssid in
deny or reject list.
Change-Id: I639f30e194fdb3f5521e0483a7b8151d48134450
CRs-Fixed: 3359171
Driver adds a BSSID to the reject list due to multiple
DE authentication triggers from associated AP. If DUT tries the
FASTREASSOC command for the same BSSID multiple times, the host
triggers disconnection to handle roaming failure, and this results
in DUT losing the current connection.
To keep the current connection DUT should not trigger a roaming
event if the BSSID is already added to the reject list in the
host.
The fix is to add logic to avoid the FASTREASSOC trigger command
for AP(s) present in the reject list of HOST.
Change-Id: I315da12b3f93d5d9d67396a5dd9e12fa2be5fda0
CRs-Fixed: 3328847
-Wimplicit-fallthrough is being enabled by default. Some compilers
such as clang require the attribute instead of just a fallthrough comment.
Change-Id: I6ddf98a20bf0d5abb3088f8f231e9be8005f15e6
CRs-Fixed: 3217409
