[systemd-devel] systemd-networkd, IPv6PrivacyExtensions=kernel, sysctl and devicenames

[Ede Wolf]

> 
> That sounds like actual bug. What systemd version do you use?

I've just did a test with Deepin, as I've had VM flying around of that 
debian based distribution, and here it seems to work, using systemd 241 
instead of 245. systemd-sysctl is clearly called after the renaming:


May 22 21:48:46 test1-PC kernel: Yama: disabled by default; enable with 
sysctl kernel.yama.*
May 22 21:48:46 test1-PC kernel: virtio_net virtio0 enp0s3: renamed from 
eth0
May 22 21:48:46 test1-PC systemd-sysctl[259]: Couldn't write 
'840b:b3d7:8121:5774:b967:1737:db42:a87b' to 
'net/ipv6/conf/eth0/stable_secret', ignoring: No such file or directory
May 22 21:48:46 test1-PC systemd-sysctl[259]: Couldn't write '2' to 
'net/ipv6/conf/eth0/addr_gen_mode', ignoring: No such file or directory
May 22 21:48:46 test1-PC systemd-sysctl[259]: Couldn't write '2' to 
'net/ipv6/conf/eth0/use_tempaddr', ignoring: No such file or directory
May 22 21:48:46 test1-PC systemd-networkd[263]: enp0s3: Gained carrier


So here eth0 is the invalid interface, as it should be.


Not sure now wether this a regression or distribution specific. Where 
are the dependencies defined what service runs first at this early stage?