Send connman mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.01.org/mailman/listinfo/connman
or, 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: [PATCH] plugins/wifi: Do not disable network on
      Disconnect (Naveen Singh)


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

Message: 1
Date: Sun, 27 Mar 2016 23:03:10 -0700
From: Naveen Singh <[email protected]>
To: Patrik Flykt <[email protected]>
Cc: [email protected], Naveen Singh <[email protected]>
Subject: Re: [PATCH] plugins/wifi: Do not disable network on
        Disconnect
Message-ID:
        <cafk1zrcgcvzj0zvbqlr4hbuci6ekte2voobqpkrzzcqr_ty...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Tue, Mar 22, 2016 at 4:57 AM, Patrik Flykt <[email protected]>
wrote:

> On Mon, 2016-03-21 at 13:23 -0700, Naveen Singh wrote:
> >         So unless the proper set of reason codes cannot be obtained
> >         from
> >         wpa_supplicant indicating that the disconnection is due to a
> >         lower level
> >         issue that can be ignored, wpa_supplicant should not be left
> >         connecting
> >         by its own.
> > Tying this up with a specific reason code may not be correct as reason
> > code are always not available. Consider an example where device
> > intermittently faced beacon loss (because of interference) and we know
> > AP exists. wpa_s will get device connected back immediately. In the
> > other case if we would have disabled the network (as reason code
> > coming with this disconnect notification is not 6, 7 or 4),
> > re-connection would have taken longer.
>
> This is the main source of issues with wpa_supplicant. It should not
> tell its users that the network disconnected until the network really
> was cut and the few immediate retries didn't succeed either.
>
> Are the reason codes sent by certain wpa_supplicant D-Bus signals
> actually documented anywhere? Last time I looked no exhaustive list was
> available, do you have any empirical evidence of the reason codes sent
> in different states due to non-terminal and terminal network disconnect
> events?
>
> Cheers,
>
>         Patrik
> Hello Patrik

What is your thought on this? Without this change, band steering/load
balancing would be very difficult to implement.
Regards
Naveen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20160327/19249712/attachment-0001.html>

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

Subject: Digest Footer

_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman


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

End of connman Digest, Vol 5, Issue 31
**************************************

Reply via email to