Send connman mailing list submissions to
        [email protected]

To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."

Today's Topics:

   1. Re: wifi AP disconnect(disconnect reason code 1) (Deepu Paul)


----------------------------------------------------------------------

Date: Thu, 9 Jan 2020 16:36:16 +0000
From: Deepu Paul <[email protected]>
Subject: Re: wifi AP disconnect(disconnect reason code 1)
To: Daniel Wagner <[email protected]>, [email protected]
Message-ID:
        <cadl1k3ne3qonxwapq5wwev2vx9xcf2hbadrvhg-agd4hl+b...@mail.gmail.com>
Content-Type: multipart/alternative;
        boundary="000000000000545f9d059bb79cdc"

--000000000000545f9d059bb79cdc
Content-Type: text/plain; charset="UTF-8"

Hi Daniel,
May i know if you a chance to look the logs below please?

Thanks
Deepu Paul

On Wed, Jan 8, 2020 at 5:28 PM Deepu Paul <[email protected]> wrote:

> Hi Daniel,
>
> Attaching both connman and wpa_supplicant logs,
>
> There are 2  disconnects with reason code 1, in the first one it
> reconnects as expected, in the second one it didn't.
>
> I am bit confused here, not sure if this an issue with wpa_supplicant.
>
> Can you please help me with the logs to find the root cause?
>
> Thanks
> Deepu Paul
>
> On Tue, Jan 7, 2020 at 8:04 AM Daniel Wagner <[email protected]> wrote:
>
>> Hi Deepu,
>>
>> On Mon, Jan 06, 2020 at 12:22:31PM +0000, Deepu Paul wrote:
>> > Hi Daniel,
>> >
>> > The previous mail got bounced back as the attachment  size was greater
>> than
>> > 500kb .
>> >
>> > 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 please
>> > 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, 10)
>> > 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[3595]: ../connman-1.37/src/rtnl.c:rtnl_message() NEWLINK len 72
>> type 16 flags 0x0000 seq 0 pid 0
>> connmand[3595]:
>> ../connman-1.37/gsupplicant/supplicant.c:signal_interface_changed()
>> connmand[3595]:
>> ../connman-1.37/gsupplicant/supplicant.c:interface_property()
>> DisconnectReason
>> connmand[3595]:
>> ../connman-1.37/gsupplicant/supplicant.c:signal_bss_removed()
>> connmand[3595]:
>> ../connman-1.37/gsupplicant/supplicant.c:update_network_signal() New
>> network signal -90
>> connmand[3595]: ../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?
>>
>> Thanks,
>> Daniel
>> _______________________________________________
>> connman mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>>
>

--000000000000545f9d059bb79cdc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Daniel,<div>May i know if you a chance=
 to look the logs below please?<br></div><div><br></div><div>Thanks</div><d=
iv>Deepu Paul</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Wed, Jan 8, 2020 at 5:28 PM Deepu Paul &lt;<a href=3D=
"mailto:[email protected]";>[email protected]</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Dan=
iel,<div><br></div><div>Attaching both connman and wpa_supplicant logs,</di=
v><div><br></div><div>There are 2=C2=A0 disconnects with reason code 1, in =
the first one it reconnects as expected, in the second one it didn&#39;t.</=
div><div><br></div><div>I am bit confused here, not sure if this an issue w=
ith wpa_supplicant.</div><div><br></div><div>Can you please help me with th=
e logs to find the root cause?</div><div><br></div><div>Thanks</div><div>De=
epu Paul</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Jan 7, 2020 at 8:04 AM Daniel Wagner &lt;<a href=3D=
"mailto:[email protected]"; target=3D"_blank">[email protected]</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Deepu,<br>
<br>
On Mon, Jan 06, 2020 at 12:22:31PM +0000, Deepu Paul wrote:<br>
&gt; Hi Daniel,<br>
&gt; <br>
&gt; The previous mail got bounced back as the attachment=C2=A0 size was gr=
eater than<br>
&gt; 500kb .<br>
&gt; <br>
&gt; Attaching the logs again.<br>
<br>
Thanks for the logs. Really helpful.<br>
<br>
&gt; one thing i am noticing is every-time during disconnect, there is<br>
&gt; a (Reason: 3=3DDEAUTH_LEAVING)[line 6790] during the re association<br=
>
&gt; after (Reason: 1=3DUNSPECIFIED)[line 5752].<br>
<br>
IIRC, deauth leaving means the local device has decided to leave the<br>
network. Though this doesn&#39;t make any difference for ConnMan. It&#39;s =
the<br>
same code path. Only reason code 6 is handled differently.<br>
<br>
&gt; I am not sure if this is the issue with wpa_supplicant, can you please=
<br>
&gt; check the logs and let me know if this is initiated by the wpa_supplic=
ant?<br>
<br>
>From you previous email:<br>
<br>
&gt; In the second one it failed, in this scenario i don&#39;t see the inte=
rface state change to 2(disconnected), in this case the state=C2=A0 change =
is (4, 5, 6, 8, 10)<br>
&gt; and seeing the message=C2=A0 &quot;Probably roaming right now! Staying=
 connected...&quot;<br>
<br>
That is what I suspected. So wpa_supplicant doesn&#39;t tell us excactly<br=
>
what it is doing. Suddenldy we see state transitions and we have to<br>
guess what&#39;s happending.<br>
<br>
But then we get a new message which it the disconnect reason:<br>
<br>
connmand[3595]: ../connman-1.37/src/rtnl.c:rtnl_message() NEWLINK len 72 ty=
pe 16 flags 0x0000 seq 0 pid 0<br>
connmand[3595]: ../connman-1.37/gsupplicant/supplicant.c:signal_interface_c=
hanged()<br>
connmand[3595]: ../connman-1.37/gsupplicant/supplicant.c:interface_property=
() DisconnectReason<br>
connmand[3595]: ../connman-1.37/gsupplicant/supplicant.c:signal_bss_removed=
()<br>
connmand[3595]: ../connman-1.37/gsupplicant/supplicant.c:update_network_sig=
nal() New network signal -90<br>
connmand[3595]: ../connman-1.37/plugins/wifi.c:network_removed() name purpl=
eline<br>
<br>
Could it be, whenever it works you don&#39;t get an disconnect reason<br>
after we assume wpa_supplicant is roaming?<br>
<br>
Thanks,<br>
Daniel<br>
_______________________________________________<br>
connman mailing list -- <a href=3D"mailto:[email protected]"; target=3D"_=
blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]=
g" target=3D"_blank">[email protected]</a><br>
</blockquote></div>
</blockquote></div></div>

--000000000000545f9d059bb79cdc--

------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]


------------------------------

End of connman Digest, Vol 51, Issue 13
***************************************

Reply via email to