On Mon, Jan 06, 2020 at 12:22:31PM +0000, Deepu Paul wrote:
The previous mail got bounced back as the attachment size was greater than
Attaching the logs again.
Thanks for the logs. Really helpful.
one thing i am noticing is every-time during disconnect, there is
a (Reason: 3=DEAUTH_LEAVING)[line 6790] during the re association
after (Reason: 1=UNSPECIFIED)[line 5752].
IIRC, deauth leaving means the local device has decided to leave the
network. Though this doesn't make any difference for ConnMan. It's the
same code path. Only reason code 6 is handled differently.
I am not sure if this is the issue with wpa_supplicant, can you
check the logs and let me know if this is initiated by the wpa_supplicant?
From you previous email:
In the second one it failed, in this scenario i don't see the
interface state change to 2(disconnected), in this case the state change is (4, 5, 6, 8,
and seeing the message "Probably roaming right now! Staying connected..."
That is what I suspected. So wpa_supplicant doesn't tell us excactly
what it is doing. Suddenldy we see state transitions and we have to
guess what's happending.
But then we get a new message which it the disconnect reason:
connmand: ../connman-1.37/src/rtnl.c:rtnl_message() NEWLINK len 72 type 16 flags
0x0000 seq 0 pid 0
connmand: ../connman-1.37/gsupplicant/supplicant.c:update_network_signal() New
network signal -90
connmand: ../connman-1.37/plugins/wifi.c:network_removed() name purpleline
Could it be, whenever it works you don't get an disconnect reason
after we assume wpa_supplicant is roaming?