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: Fri, 21 Feb 2020 10:05:44 +0000
From: Deepu Paul <[email protected]>
Subject: Re: wifi AP disconnect(disconnect reason code 1)
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<CADL1K3mx371hs0W-Gd=0gopshfg1qdw1pspu5ehprznmfmw...@mail.gmail.com>
Content-Type: multipart/mixed; boundary="000000000000da5051059f132a93"
--000000000000da5051059f132a93
Content-Type: multipart/alternative; boundary="000000000000da504e059f132a91"
--000000000000da504e059f132a91
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
I have a better fix now for the wifi disconnect with reason code 1.
Attaching the patch. Ideally both the patch works as expected.
Thanks
Deepu Paul
On Fri, Jan 10, 2020 at 11:27 AM Deepu Paul <[email protected]> wrote:
> Hi Daniel,
>
> Yes, auto connect is configured TRUE.
>
>
>
>
>
>
>
>
>
> * Type = wifi Security = [ psk ] State = failure Error = blocked
> Strength = 73 Favorite = True Immutable = False AutoConnect = True Name
> = purpleline*
>
> There are 2 BSSID's 6c:fa:89:55:ce:7a and 58:0a:20:5b:ec:ca for the ssid
> "purpleline" (2 access points with the same network )
>
> Not sure that is the problem?
>
> Thanks
> Deepu Paul
>
>
> On Fri, Jan 10, 2020 at 8:40 AM Daniel Wagner <[email protected]> wrote:
>
>> Hi
>>
>> Please don't top post and also send text emails.
>>
>> On Thu, Jan 09, 2020 at 04:36:16PM +0000, Deepu Paul wrote:
>> > May i know if you a chance to look the logs below please?
>>
>> Yes.
>>
>> > > 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?
>>
>> It looks like the first reconnects is triggered by the event from
>> wpa_supplicant with scan results.
>>
>> But in both cases the state machine for the sevices seems to work.
>> online -> disconnect/failure -> idle. Then the autoconnect code kicks
>> in. Could it be that in the first case the scan_results trigger the
>> autoconnect differently then the regular case? Is the service
>> configured as autoconnect?
>>
>> Thanks,
>> Daniel
>> _______________________________________________
>> connman mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>>
>
--000000000000da504e059f132a91
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Daniel,<div><br></div><div>I have a better fix now for =
the wifi disconnect with reason code 1.</div><div>Attaching the patch. Idea=
lly both the patch works as expected.</div><div><br></div><div>Thanks</div>=
<div>Deepu Paul</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Fri, Jan 10, 2020 at 11:27 AM Deepu Paul <<a hre=
f=3D"mailto:[email protected]";>[email protected]</a>> 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"><div dir=3D"ltr">Hi=
Daniel,<div><br></div><div>Yes, auto connect is configured TRUE.</div><div=
><br></div><div><i>=C2=A0 Type =3D wifi<br>=C2=A0 Security =3D [ psk ]<br>=
=C2=A0 State =3D failure<br>=C2=A0 Error =3D blocked<br>=C2=A0 Strength =3D=
73<br>=C2=A0 Favorite =3D True<br>=C2=A0 Immutable =3D False<br>=C2=A0 Aut=
oConnect =3D True<br>=C2=A0 Name =3D purpleline</i><br></div><div><br></div=
><div>There are 2=C2=A0 BSSID's 6c:fa:89:55:ce:7a and=C2=A0 58:0a:20:5b=
:ec:ca for the ssid "purpleline" (2 access points with the same n=
etwork )=C2=A0</div><div><br></div><div>Not sure that is the problem?</div>=
<div><br></div><div>Thanks<br></div><div>Deepu Paul</div><div><br></div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Fri, Jan 10, 2020 at 8:40 AM Daniel Wagner <<a href=3D"mailto:wagi@monom=
.org" target=3D"_blank">[email protected]</a>> wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">Hi<br>
<br>
Please don't top post and also send text emails.<br>
<br>
On Thu, Jan 09, 2020 at 04:36:16PM +0000, Deepu Paul wrote:<br>
> May i know if you a chance to look the logs below please?<br>
<br>
Yes.<br>
<br>
> > Attaching both connman and wpa_supplicant logs,<br>
> ><br>
> > There are 2=C2=A0 disconnects with reason code 1, in the first on=
e it<br>
> > reconnects as expected, in the second one it didn't.<br>
> ><br>
> > I am bit confused here, not sure if this an issue with wpa_suppli=
cant.<br>
> ><br>
> > Can you please help me with the logs to find the root cause?<br>
<br>
It looks like the first reconnects is triggered by the event from<br>
wpa_supplicant with scan results.<br>
<br>
But in both cases the state machine for the sevices seems to work.<br>
online -> disconnect/failure -> idle. Then the autoconnect code kicks=
<br>
in. Could it be that in the first case the scan_results trigger the<br>
autoconnect differently then the regular case? Is the service<br>
configured as autoconnect?<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>
--000000000000da504e059f132a91--
--000000000000da5051059f132a93
Content-Type: text/x-patch; charset="US-ASCII";
name="0001-wifi.c-wifi-AP-disconnect-with-reason-code-1-and-doe.patch"
Content-Disposition: attachment;
filename="0001-wifi.c-wifi-AP-disconnect-with-reason-code-1-and-doe.patch"
Content-Transfer-Encoding: base64
Content-ID: <f_k6w0cw440>
X-Attachment-Id: f_k6w0cw440
RnJvbSBhYmExYWNiMDc5NDE4YzRlYmQ3ZDExMmYzZTRlZWI5YjEyNDk3MTg1IE1vbiBTZXAgMTcg
MDA6MDA6MDAgMjAwMQpGcm9tOiBEZWVwdSBQYXVsIDxkZWVwdS5wYXVsQGpjaS5jb20+CkRhdGU6
IEZyaSwgMjEgRmViIDIwMjAgMDk6MTE6MTQgKzAwMDAKU3ViamVjdDogW1BBVENIXSB3aWZpLmM6
IHdpZmkgQVAgZGlzY29ubmVjdCB3aXRoIHJlYXNvbiBjb2RlIDEgYW5kIGRvZXNuJ3QKIHJlY29u
bmVjdAoKcHVycGxlbGluZShjaXNjbyByb3V0ZXIpIHJlLWF1dGhlbnRpY2F0ZXMgZXZlcnkgMzAg
bWlucyBhbmQga2lja3MKb3V0IHRoZSBjb25uZWN0aW9uIHdpdGggcmVhc29uIGNvZGUgMSwgY29u
bm1hbiBhc3N1bWVzIGl0cyBibG9ja2VkCmJ5IHRoZSBBUCBhbmQgc2V0cyB0aGUgbmV0d29yayBl
cnJvciBjb2RlIGFzCiJDT05OTUFOX05FVFdPUktfRVJST1JfQkxPQ0tFRCIsIHRoaXMgdHJpZ2dl
cnMgbmV0d29ya19kaXNjb25uZWN0IG1ldGhvZAp3aGljaCBjYWxscyB0aGUgd3BhIHN1cHBsaWNh
bnQgaW50ZXJmYWNlIGdfc3VwcGxpY2FudF9pbnRlcmZhY2VfZGlzY29ubmVjdAp0byBkaXNjb25u
ZWN0IHRoZSBuZXR3b3JrIGFuZCB0aGUgc3RhdGUgaXMgImJsb2NrZWQiLiBpZiB0aGlzIGlzIG5v
dApibG9ja2VkIHRoZSBuZXh0ICJzdGFydF9zY2FuIiBpbiBjYXNlIEdfU1VQUExJQ0FOVF9TVEFU
RV9ESVNDT05ORUNURUQ6CndpbGwgYXV0byBjb25uZWN0IHRvIHRoZSBjdXJyZW50IG5ldHdvcmsv
cGVuZGluZyBuZXR3b3JrLgoKWEhGLTY4ODogRml4IHRoZSBXaUZpIGRpc2Nvbm5lY3Rpb24KLS0t
CiBwbHVnaW5zL3dpZmkuYyB8IDEgKwogMSBmaWxlIGNoYW5nZWQsIDEgaW5zZXJ0aW9uKCspCgpk
aWZmIC0tZ2l0IGEvcGx1Z2lucy93aWZpLmMgYi9wbHVnaW5zL3dpZmkuYwppbmRleCBmOGMyMmJl
Li4yMDM0NDJjIDEwMDY0NAotLS0gYS9wbHVnaW5zL3dpZmkuYworKysgYi9wbHVnaW5zL3dpZmku
YwpAQCAtMjU0NCw2ICsyNTQ0LDcgQEAgc3RhdGljIHZvaWQgaW50ZXJmYWNlX3N0YXRlKEdTdXBw
bGljYW50SW50ZXJmYWNlICppbnRlcmZhY2UpCiAJCXN3aXRjaCAod2lmaS0+ZGlzY29ubmVjdF9j
b2RlKSB7CiAJCWNhc2UgMTogLyogVW5zcGVjaWZpZWQgcmVhc29uICovCiAJCQkvKiBMZXQncyBh
c3N1bWUgaXQncyBiZWNhdXNlIHdlIGdvdCBibG9ja2VkICovCisJCQlicmVhazsKIAogCQljYXNl
IDY6IC8qIENsYXNzIDIgZnJhbWUgcmVjZWl2ZWQgZnJvbSBub25hdXRoZW50aWNhdGVkIFNUQSAq
LwogCQkJY29ubm1hbl9uZXR3b3JrX3NldF9lcnJvcihuZXR3b3JrLAotLSAKMi4yMC4xCgo=
--000000000000da5051059f132a93--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 21
***************************************
