Send connman mailing list submissions to
connman@lists.01.org
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
connman-requ...@lists.01.org
You can reach the person managing the list at
connman-ow...@lists.01.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: VLAN configuration support (Daniel Wagner)
2. Re: [PATCH] wifi: reduce background scanning threshold from
-45 to -65 (Daniel Wagner)
3. Re: IPv6 privacy extensions with connman (Daniel Wagner)
4. Re: IPv6 privacy extensions with connman (Christian)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Apr 2019 08:27:11 +0200
From: Daniel Wagner <w...@monom.org>
To: "Langlois, Maxime" <maxime.langl...@grassvalley.com>
Cc: "connman@lists.01.org" <connman@lists.01.org>
Subject: Re: VLAN configuration support
Message-ID: <3b609050-d689-3fe0-c3a3-8acf14f0e...@monom.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Maxime,
On 4/4/19 10:25 PM, Langlois, Maxime wrote:
> would love to contribute! However I haven't planned that extra time for
> diving into the connman source code... and deadlines being what they
> are, I might have to move to an alternative :(
Fair enough. Anyway, you should plan some time to fix/maintain any open
source project you choose. There is no free lunch.
The change isn't too hard to implement and test. I'll do it in the
coming days.
> Decision is not yet made though, as I still have other things to
> evaluate. Our networking requirements are quite complex and I'm still
> trying to figure every bits and pieces!
Sure :)
> If it ever occurs that I retain the connman solution, I certainly might
> submit the patches.
That is good to hear!
Thanks,
Daniel
------------------------------
Message: 2
Date: Tue, 16 Apr 2019 08:45:30 +0200
From: Daniel Wagner <w...@monom.org>
To: Julien Massot <massot.jul...@gmail.com>
Cc: connman@lists.01.org
Subject: Re: [PATCH] wifi: reduce background scanning threshold from
-45 to -65
Message-ID: <37030a6e-7d58-d0bd-4cde-f172bada0...@monom.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Julien,
On 4/8/19 9:48 AM, Julien Massot wrote:
> From: Julien Massot <jmas...@softbankrobotics.com>
>
> The background scanning is intended for potential roaming
> purpose.
>
> An RSSI of -45 is a really good signal level and should not
> trigger a background scan intended for roaming.
>
> -65 is the beginning of wifi trouble and most likely we may
> want to move to a better BSS.
Patch applied.
Thanks,
Daniel
------------------------------
Message: 3
Date: Tue, 16 Apr 2019 08:58:17 +0200
From: Daniel Wagner <w...@monom.org>
To: Christian <list-christ...@web.de>, connman@lists.01.org
Subject: Re: IPv6 privacy extensions with connman
Message-ID: <b912b312-929b-3254-a9ef-dabdd04bd...@monom.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Christian,
On 4/10/19 5:31 PM, Christian wrote:
> I am trying to activate IPv6 with privacy extension. (On a Libreelec
> system, running on a Raspberry Pi 3).
>
> First, I encountered a spelling mistake: The option for "IPv6.privacy"
> actually has to be spelled "prefered" to work. With the correct spelling
> "preferred" nothing happened. Only after changing it to the wrong
> spelling a second IPv6 was generated and the option showed up in the
> service (listed as: Privacy=prefered).
Thanks for the report. Which version do you use? There is code in place
to handle both versions of the word. Maybe we missed a place.
> Second, after setting the privacy option to "prefered", I get an
> additional IPv6, however it is set as "scope global secondary dynamic".
> Privacy extensions should normally be "scope global temporary dynamic"
> and get deprecated after some time.
Need to check this. Sounds like a miss configuration in ConnMan.
> Am I having the wrong configuration here or are these bugs?
Don't think so.
Thanks,
Daniel
------------------------------
Message: 4
Date: Tue, 16 Apr 2019 11:43:20 +0200
From: Christian <list-christ...@web.de>
To: connman@lists.01.org
Subject: Re: IPv6 privacy extensions with connman
Message-ID: <d3c7b5a47b8d678b4d1e88ee69acdc8cb6f47e0f.ca...@web.de>
Content-Type: text/plain; charset="utf-8"
Hi Daniel,
I just updated to newer version of libreelec (RPi2.arm-devel-
20190413210320-#0413-g977b2aa) and this runs connman 1.37. If you want
to try it yourself, you find it here:
https://forum.kodi.tv/showthread.php?tid=298461However I only saw the
version 1.37 in the update notes. Is there a way to check the version
via connmanctl? I did not see an option.
When asking my question, the version must have been at least 1.36 (also
only derived from libreelec update notes).
Regarding the spelling of preferred, I think any wrong spelling should
be purged. I know that it is well meant to be fault tolerant, but it is
massively confusing.
Thanks for looking into this! Looking forward on what you will find on
the secondary/temporary thing.
Kind Regards Christian
Am Dienstag, den 16.04.2019, 08:58 +0200 schrieb Daniel Wagner:
> Hi Christian,
> On 4/10/19 5:31 PM, Christian wrote:
> I am trying to activate IPv6 with privacy extension. (On a Libreelec
> system, running on a Raspberry Pi 3).
> First, I encountered a spelling mistake: The option for
> "IPv6.privacy" actually has to be spelled "prefered" to work. With
> the correct spelling "preferred" nothing happened. Only after
> changing it to the wrong spelling a second IPv6 was generated and the
> option showed up in the service (listed as: Privacy=prefered).
> Thanks for the report. Which version do you use? There is code in
> place to handle both versions of the word. Maybe we missed a place.
> Second, after setting the privacy option to "prefered", I get an
> additional IPv6, however it is set as "scope global secondary
> dynamic". Privacy extensions should normally be "scope global
> temporary dynamic" and get deprecated after some time.
> Need to check this. Sounds like a miss configuration in ConnMan.
> Am I having the wrong configuration here or are these bugs?
> Don't think so.
> Thanks,Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20190416/b9a09b03/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
connman@lists.01.org
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 42, Issue 9
**************************************
