IPv6 Privacy Extensions are disabled, by default.
Not yet known.
None.
It is possible to enable them back using the terminal.
nmcli connection and check what the UUID for the relevant interface is, and copy it.nmcli connection modify <uuid> ipv6.ip6-privacy 2, replacing <uuid> with the relevant UUID.You may need to run these with sudo? Unsure.
One thing I’d like to add, is that from the distros I’ve used, Linux Mint, did not have this issue, but Linux Mint Debian Edition did, so I suppose Ubuntu fixed this. On LMDE, it was easy to fix without the terminal by going into network settings and then connections, and there all that can be done through a GUI.
The weird thing is that the option marked as ‘Default’ there, seems to just not use them.
I’m unsure if this could potentially have been being caused by my network. I think my network has DHCPv6 for DNS only (for an address that doesn’t have port 53 open… but anyway) but uses regular SLAAC for addressing. Maybe Linux thinks I’m using DHCPv6 because of that and doesn’t deal with this properly…? The only reason I even think I might have DHCPv6 is because AOSP doesn’t get these bad DNS addresses (it’s the router’s local link address) while other OSes do.
I believe this is a bug really, unless it’s something really weird with my setup, but it’s weird it wasn’t an issue in Linux Mint regular, using Ubuntu.
For servers, keeping IPv6 privacy extensions off might make sense, as they’d probably want to use a stable IPv6 address there anyway, but not for workstations, regular desktop use.
From Proposed Common Issues to Ask Fedora
Ended up turning this into a bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=2280924
This shouldn’t be considered normal in workstations.
You should investigate possible negative effects if you want to enable this option by default: