It doesn't overrule it. Please make sure you set net.ipv6.conf.default.use_tempaddr to 0 in 10-ipv6-privacy.conf (or in /etc/sysctl.conf, etc.) if you want it to not be set. Alternatively, you may want to set "ip6-privacy=0" in the configuration file for your connection (under /etc/NetworkManager/system-connections/).
This isn't changing the value in a default release. The issue was that for default automatically generated connections for wired devices, NM was trying to be clever and reading a file we don't actually keep the ipv6 use_tempaddr setting in, and thus always setting it to 0.
If you're running into problems with this, please make sure you file a separate bug and define all the information specific to your system, such as what is set in /etc/sysctl.conf and /etc/sysctl.d/10-ipv6-privacy.conf, as well as whatever connection file might be relevant (in case the values are set in there). Then refer to your new bug here so we can look into it ASAP.
It doesn't overrule it. Please make sure you set net.ipv6. conf.default. use_tempaddr to 0 in 10-ipv6- privacy. conf (or in /etc/sysctl.conf, etc.) if you want it to not be set. Alternatively, you may want to set "ip6-privacy=0" in the configuration file for your connection (under /etc/NetworkMan ager/system- connections/ ).
This isn't changing the value in a default release. The issue was that for default automatically generated connections for wired devices, NM was trying to be clever and reading a file we don't actually keep the ipv6 use_tempaddr setting in, and thus always setting it to 0.
If you're running into problems with this, please make sure you file a separate bug and define all the information specific to your system, such as what is set in /etc/sysctl.conf and /etc/sysctl. d/10-ipv6- privacy. conf, as well as whatever connection file might be relevant (in case the values are set in there). Then refer to your new bug here so we can look into it ASAP.