Denis,

I see a similar result, though the mechanism may be different, on an x86
laptop also running Arch Linux. I use iwd with NetworkManager on this
computer and if I do the same thing (restart radio on router), it also does
not reconnect. NM is 1.28.1dev+7+g3f5df3cdc6 and iwd is v1.11. If it is
force disconnected from the router it never tries to reconnect. If I select
it from the drop down, it reconnects.

I noticed that NM did not set 'AutoConnect=true' in the
/var/lib/iwd/spg3.psk file, so I added it and verified that iwctl reports
that this feature is set (It did not before), but even after this was
added, it does not reconnect when it is forced off the network by
rebooting, disconnecting or cycling the radio.

The iwd-monitor log shows lots of this:
{Station} [/net/connman/iwd/0/4] Scanning = False
{Station} [/net/connman/iwd/0/4] Scanning = True
{Station} [/net/connman/iwd/0/4] Scanning = False
{Station} [/net/connman/iwd/0/4] Scanning = True
{Removed net.connman.iwd.Network}
[/net/connman/iwd/0/4/426964656e486172726973_psk]
{Added net.connman.iwd.Network}
[/net/connman/iwd/0/4/4e4554474541523336_psk]
      Name = NETGEAR36
      Connected = False
      Device = /net/connman/iwd/0/4
      Type = psk
{Station} [/net/connman/iwd/0/4] Scanning = False
{Station} [/net/connman/iwd/0/4] Scanning = True
{Added net.connman.iwd.Network}
[/net/connman/iwd/0/4/415454687a4366547869_psk]
      Name = ATThzCfTxi
      Connected = False
      Device = /net/connman/iwd/0/4
      Type = psk
{Added net.connman.iwd.Network} [/net/connman/iwd/0/4/5261676e6172_psk]
      Name = Ragnar
      Connected = False
      Device = /net/connman/iwd/0/4
      Type = psk
{Removed net.connman.iwd.Network}
[/net/connman/iwd/0/4/4d65617374657761_psk]
{Removed net.connman.iwd.Network}
[/net/connman/iwd/0/4/41545470666b766e4378_psk]
{Added net.connman.iwd.Network}
[/net/connman/iwd/0/4/4e4554474541523539_psk]
      Name = NETGEAR59
      Connected = False
      Device = /net/connman/iwd/0/4
      Type = psk
{Station} [/net/connman/iwd/0/4] Scanning = False
...

Interestingly, none of the logs I made actually showed that iwd had scanned
and found the network that it was just previously connected to in the list
of Network Names. While scanning, it sees the 2.5 network on the same
router, but not the 5Ghz that it knows the password to. If I do a 'iwctl
wlan0 get-networks', the 5Ghz radio is at the top of the list but it does
not connect to it. As soon as I select it in the drop down in NM it
connects.

My questions: With NM, is it supposed to have an 'AutoConnect=true' in the
psk file? If so, it does not appear that NM creates that in the psk file.
Why does the scan not pick up the previously connected SSID?

I just tried this again on the RPi and now, today, it reconnects when I
force a disconnect. I have no idea what changed. It absolutely did not
yesterday or the day before. I did  not even reboot the Pi. It also scanned
but never saw the SSID I was intending to use.

Regards,

Keith

On Mon, Feb 8, 2021 at 3:32 PM KeithG <ys3al35l@gmail.com> wrote:

> On Mon, Feb 8, 2021 at 1:53 PM Denis Kenzior <denkenz@gmail.com> wrote:
>
>>
>> To me, it looks like scanning is being driven over D-Bus by invoking
>> Station.Scan().  It also looks like autoconnect has been forced off,
>> perhaps via
>> Station.Disconnect() being invoked?  Hard to tell from this log, but
>> looks iwd
>> isn't trying to autoconnect and would instead rely on connman to trigger
>> the
>> connection.
>>
>> Regards,
>> -Denis
>>
> Denis,
>
> The /var/lib/iwd/*.psk file has "AutoConnect=true" set. I did notice that
> last night it had been reset somehow to false after I sent those partial
> logs, but I reset it to true today and still do not get a reconnect.
>
> Running the dbus-monitor script shows exactly that. it gets a
> {Station} [/net/connman/iwd/0/3] Scanning = True
> then False periodically, but it never connects. I'll post again on connman
> mail list to see what may need to be adjusted.
>
> If I restart iwd, it connects right away.
>
> Regards,
> Keith
>