Il 29/03/2021 18:12, Denis Kenzior ha scritto:
> So in theory this should always be happening. Once iwd is in
> 'autoconnect' state (starting state, or when we lose a connection)
> then any scan results triggered (either internal scanning logic or
> scans triggered via dbus/iwctl) should then be considered for
> autoconnect purposes. You say that 'it's not always the case'.
Indeed. AP disappears. Some time passes. I issue a 'station <net> scan'.
In some cases, iwd immediately connects to a known network. In some
other cases, I can see it with 'station <net> get-networks', but nothing
happens. Issuing a manual 'connect' will bring the network up
> Also, are you running any other network managers on top of iwd
> just iwd standalone?
I'm using iwd standalone.
On Mon, Mar 29 2021, Mauro Condarelli wrote:
I am guessing he needs to re-enter 'autoconnect' state after
I didn't explicitly disconnect in this case, but this makes me wonder if
iwd can exit the 'autoconnect' state by itself for some other reason.
Use case for this would be to disconnect from the currently
net and try to connect to some other, if available.
What would be command sequence for this?
Would be curious about that too.