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 v3] gsupplicant: Optimize AddNetwork Handler by
avoiding DBUS call. (Patrik Flykt)
2. Re: [PATCH] doc: Fixed typo mistakes (Patrik Flykt)
3. Re: [PATCH] plugins/wifi: Do not disable network on
Disconnect (Patrik Flykt)
----------------------------------------------------------------------
Message: 1
Date: Tue, 22 Mar 2016 12:53:14 +0200
From: Patrik Flykt <[email protected]>
To: [email protected]
Cc: [email protected], Naveen Singh <[email protected]>
Subject: Re: [PATCH v3] gsupplicant: Optimize AddNetwork Handler by
avoiding DBUS call.
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Thu, 2016-03-17 at 17:33 -0700, [email protected] wrote:
> From: Naveen Singh <[email protected]>
>
> In case network path is not NULL, network should only be removed
> if the new network (to be added) is different from what is sitting
> in wpa_supplicant. This would avoid two DBUS calls: AddNetwork and
> SelectNetwork.
This was also applied, thanks!
Patrik
------------------------------
Message: 2
Date: Tue, 22 Mar 2016 12:56:46 +0200
From: Patrik Flykt <[email protected]>
To: Nishant Chaprana <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH] doc: Fixed typo mistakes
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Thu, 2016-03-10 at 10:42 +0530, Nishant Chaprana wrote:
> - "enabled" or "preferred" (or the misspelled "prefered"). See use_tempaddr
> + "enabled" or "preferred" (or the misspelled "preferred"). See use_tempaddr
The option was earlier misspelled as 'prefered' with one 'r', the option
was later corrected to be 'preferred' with two 'r's, but the previous
spelling had to be left in place in order not to break anything. Please
don't correct the spelling of this, it's supposed to be misspelled...
Cheers,
Patrik
------------------------------
Message: 3
Date: Tue, 22 Mar 2016 13:57:19 +0200
From: Patrik Flykt <[email protected]>
To: Naveen Singh <[email protected]>
Cc: [email protected], Naveen Singh <[email protected]>
Subject: Re: [PATCH] plugins/wifi: Do not disable network on
Disconnect
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
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
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 5, Issue 27
**************************************
