On Thu, Sep 24, 2020 at 07:56:33AM -0500, KeithG wrote:
I pulled the latest connman and was able to run monitor-connman. The
attached log is what I got when I:
1) stopped connman
2) started connman
3) turned off the radio
4) waited until my phone and other devices were online with that SSID
5) typed 'connmanctl scan wifi' got no return
6) typed ctrl c
7) typed 'connmanctl services'
I noted that after I initiated the scan even though connman reported
nothing, it had already begun the connection and connected. We have noticed
that if we type 'iwctl station wlan0 scan' or, apparently 'connmanctl scan
wifi' that it will initiate and complete a scan. I wonder if the fact that
connman 1.38 never returns with a scan complete message is a hint?
IIRC, this is what I saw a few weeks back ago as well. ConnMan depends
on iwd to return a scan complete message. If that never happens for some
reason, the Scan() call will block until it hits a timeout (I think).
monitor-connman.txt is what showed in the terminal when I ran the script.
The monitor-connman-journal.txt is what appeared in the journal for u-
connman. At the same time the journalctl -iwd shows this:
Sep 24 07:29:14 keith-dell iwd: Received Deauthentication event,
reason: 3, from_ap: false
Sep 24 07:39:08 keith-dell iwd: Received Deauthentication event,
reason: 3, from_ap: true
Sep 24 07:39:08 keith-dell iwd: Connected BSS not in scan results
Sep 24 07:39:08 keith-dell iwd: authentication timed out
Is there some sort of timing problem?
I am no expert on iwd. Those log message look interesting, sure things
to check up what the impact is of it.