Re: Does a AP get blacklisted if it fails auth too many times?

Hi,

On 2/26/25 10:34 AM, Bryce Johnson wrote:
> On Wed, Feb 26, 2025 at 11:12 AM Bryce Johnson <[email protected]> wrote:
>> On Wed, Feb 26, 2025 at 11:00 AM James Prestwood <[email protected]> wrote:
> <snip>
>>> [1]
>>> https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/src/station.c#n286
>> Thanks James!  I'll check that out.  For also headless device use
>> case, we are never moving and only provisioned to one AP.  So we'd
>> like to try as hard as possible to stay connected to the AP.
>>
>>
> Looking into the logs a little more I did see the same message:
> 2025-02-26 00:13:56.071769752
> src/station.c:station_autoconnect_next() autoconnect: No suitable
> BSSes found
>
> Although it did reconnect automatically after that.  So it seems like
> it got around that blacklist eventually once in the log.  The more
> serious issue was at 2025-02-26 02:47 where it seems like it
> disconnected and never tried again.
>
>
> I did see after this event:
>   2025-02-26 02:47:54.473847839  event: state, old: autoconnect_quick,
> new: disconnected

This is due to something issuing a DBus Disconnect() call:

2025-02-26 02:47:54.473604731  src/station.c:station_dbus_disconnect()

If IWD gets a disconnect from DBus that actually disables autoconnect 
until a DBus Connect() call. If this is being done from any automated 
tooling you have to be _very_ sure you manually connect again, otherwise 
IWD will just sit there forever.

>
> I never saw any autoconnect messages (either trying to connect or
> autoconnect: No suitable BSSes found) for the next 2 hours until we
> restarted
> Here that ssid on was a Processing BSS from a full scan 2 hr later
> 2025-02-26 04:47:04.262785719  src/station.c:station_print_scan_bss()
> Processing BSS '9a:47:32:d9:93:fa' with SSID: revelotest1, freq: 2457,
> rank: 591, strength: -3600, data_rate: 72.2, load: 29/255, clients: 12
>
> I can share the full log if that would be useful?
>
> Bryce