On Wed, Dec 20, 2023 at 07:33:06PM -0500, pgnd wrote: > i've created a udev rule to set IPv6 params > > cat /etc/udev/rules.d/01-enp5s0-sysctl.rules > ACTION=="add|bind|change", SUBSYSTEM=="net", KERNEL=="enp5s0", \ > RUN+="/sbin/sysctl -qw \ > net.ipv6.conf.enp5s0.forwarding=0 \ > net.ipv6.conf.enp5s0.accept_ra=1 \ > net.ipv6.conf.enp5s0.use_tempaddr=1 \ > " > > but, immediately after boot, exec > > sysctl \ > net.ipv6.conf.enp5s0.forwarding \ > net.ipv6.conf.enp5s0.accept_ra \ > net.ipv6.conf.enp5s0.use_tempaddr > > returns the values, unchanged, > > net.ipv6.conf.enp5s0.forwarding = 0 > net.ipv6.conf.enp5s0.accept_ra = 0 > net.ipv6.conf.enp5s0.use_tempaddr = 0 > > otoh, if i exec at shell, > > udevadm trigger > sysctl \ > net.ipv6.conf.enp5s0.forwarding \ > net.ipv6.conf.enp5s0.accept_ra \ > net.ipv6.conf.enp5s0.use_tempaddr > > the values are changed > > net.ipv6.conf.enp5s0.forwarding = 0 > net.ipv6.conf.enp5s0.accept_ra = 1 > net.ipv6.conf.enp5s0.use_tempaddr = 1 > > what's keeping my udev rule from setting up the interface sysctls on boot? Are you sure that your rule is running after the interface is renamed? Try running 'udevadm monitor' to watch the events to ensure they are what you think they are. Anyway, try asking on the systemd mailing list, which is where udev help can be found, this list really isn't alive anymore at all, sorry. good luck! greg k-h
