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 <pauldeepu16(a)gmail.com> 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 <wagi(a)monom.org> 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 -- connman(a)lists.01.org
> To unsubscribe send an email to connman-leave(a)lists.01.org
>