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
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.