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

> >
> >
> > 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 had 2 dbus disconnects
2025-02-26 02:47:02.070527979  src/station.c:station_dbus_disconnect()
2025-02-26 02:47:54.473604731  src/station.c:station_dbus_disconnect()

Which seem to line up with Connman
2025-02-26 02:47:02.050964651  connmand[2131]: Interface wlan0 [ wifi
] error "invalid-key"
2025-02-26 02:47:02.053646583  connmand[2131]: Interface wlan0 [ wifi
] state is failure
<SNIP>
2025-02-26 02:47:54.453669827  connmand[2131]: Interface wlan0 [ wifi
] error "invalid-key"
2025-02-26 02:47:54.457083997  connmand[2131]: Interface wlan0 [ wifi
] state is failure

It probably is the one sending the dbus disconnect, doh.  For this
product we aren't actually using connman (version 1.43) for much, but
got carried along the way.  A little annoying that we are doing
everything with iwd and connman looks to be seeing the invalid key and
causing a disconnect.  Originally we were doing our provisioning with
connman using dbus, but switched to iwd directly because there seemed
like issues staying in sync.