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 2/2] doc: Update Security values for services
(Daniel Wagner)
2. Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway (KARBOWSKI Piotr)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Jan 2018 10:09:14 +0100
From: Daniel Wagner <[email protected]>
To: Jose Blanquicet <[email protected]>
Cc: Robert Tiemann <[email protected]>, [email protected]
Subject: Re: [PATCH 2/2] doc: Update Security values for services
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
On 01/23/2018 02:46 PM, Robert Tiemann wrote:
> ---
> doc/service-api.txt | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/doc/service-api.txt b/doc/service-api.txt
> index b5b4fab..4026e7e 100644
> --- a/doc/service-api.txt
> +++ b/doc/service-api.txt
> @@ -187,8 +187,15 @@ Properties string State [readonly]
> present and contains the list of security methods
> or key management settings.
>
> - Possible values are "none", "wep", "psk", "ieee8021x"
> - and also "wps".
> + Possible values are "none", "wep", "psk", "ieee8021x",
> + and also "wps" and "wps_advertising".
> +
> + Value "wps" means that the service supports WPS. A
> + service advertising itself as WPS registrar contains
> + the additional value "wps_advertising" for as long as
> + it is advertising. That is, while "wps_advertising" is
> + listed, WPS is active and it should be possible to
> + connect to the corresponding service via WPS.
This looks quite sane to me. Jose, if don't have any objections, I am
going to apply both patches.
Thanks,
Daniel
------------------------------
Message: 2
Date: Wed, 24 Jan 2018 20:05:09 +0100
From: KARBOWSKI Piotr <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Daniel,
On 01/21/2018 07:42 PM, Daniel Wagner wrote:
> The ignore interface is the simplest way to avoid the cleanup code.
> plugins/ethernet.c is not compiled in when --disable-ethernet is used
> and there is no connection to the code snippet above. That is why
> ConnMan wipes your configuration.
>
> Not sure what the best way is to address this.
>
> Some ideas:
>
> 1) The ignore device code is already there and works. So no more code
> needed, no code bloat and works.
>
> 2) Adding a no-ethernet plugin which adds all ethernet interfaces to the
> ignore list. Do we want to support interface renaming?
>
> 3) Teaching the core to ignore the ethernet devices when
> --disable-ethernet is used (filter devices out with
> CONNMAN_DEVICE_TYPE_ETHERNET).
>
> Furthermore, not only ethernet interfaces should be addressed.
>
> Thoughts?
The no-ethernet plugin sounds like overkill to me, what do you think
about a whitelist of technologies? I'd like to tell connman to touch
only wireless devices, if unset, the current behaviour would be
preserved. The cleanup would need to validate the interface before
wiping it tho.
If that's not the way to go I can live with the blacklist of br* and
eth* added locally.
Thanks.
-- Piotr.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 27, Issue 20
***************************************
