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

Hi Christian, On 4/16/19 11:43 AM, Christian wrote: 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. On startup ConnMan will print the version number. I suppose you will find in the log files. 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. The wrong spelling is not mentioned except for - IPv6.Privacy: IPv6 privacy option. Value can be either "disabled", "enabled" or "preferred" (or the misspelled "prefered"). Seeuse_tempaddr variable description in Linux kernel Documentation/networking/ip-sysctl.txt file. and the code just excepts 'prefered' as alternative. Whenever we do a major update we can also drop that part. Thanks,Daniel

Were you able to investigate why a "scope global secondary dynamic" address is created instead of a "scope global temporary dynamic".

not that I know of. The secondary dynamic address was only created after fiddling with the connman settings. I could not find any other config options for ipv6 in libreelec. Is there a way to figure out what created the IPv6?