| 8 Aug 2025 |
 emily | also, it can be set in networkd.conf | 17:14:09 |
| emily | so we don't need a separate .network for it | 17:14:16 |
| emily | ah I guess the kernel preference is per-interface | 17:15:41 |
| emily | systemd.network.config.networkConfig.IPv6PrivacyExtensions = lib.mkDefault true; should do it, though | 17:15:50 |
| emily | btw (sorry for doing this on Matrix rather than leaving reviews, I haven't had the time to do a proper substantive review) is there a reason you got bash out of the iptables closure rather than just disabling iptables? it's pretty legacy itself at this point, and systemd is dropping support for it in 259 | 17:17:02 |
| emily | * The legacy iptables support through libiptc will be removed in v259.
Only nftables backend will be supported by systemd-networkd and
systemd-nspawn since v259.
| 17:17:10 |
 ElvishJerricco | I'm pretty sure this doesn't actually work. Have you checked that the expected things actually get set with interfaces that are actually configured with networkd? With networkd, an interface only ever applies a single .network file, and drop-ins for that file; the first one whose Match section matches it. So if I've got a 40-eth0.network, this 99-default-ipv6-privacy-extensions.network won't apply to my eth0 it at all. | 19:29:40 |
| ElvishJerricco | emily's idea of just adding a default value for that directive in the networkConfig option would fix that. | 19:30:48 |
