systemd-sysctl doesn't parse /proc paths correctly like sysctl does. # cat 99-sysctl.conf net.ipv4.conf.enp3s0/200.proxy_arp_pvlan=1 net.ipv4.conf.enp3s0/200.forwarding=1 net.ipv4.conf.enp3s0/100.forwarding=1 net.ipv4.conf.enp5s0.forwarding=1 # SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-sysctl [...] Setting 'net/ipv4/conf/enp3s0/200/proxy_arp_pvlan' to '1' Failed to write '1' to '/proc/sys/net/ipv4/conf/enp3s0/200/proxy_arp_pvlan': No such file or directory Setting 'net/ipv4/conf/enp3s0/200/forwarding' to '1' Failed to write '1' to '/proc/sys/net/ipv4/conf/enp3s0/200/forwarding': No such file or directory Setting 'net/ipv4/conf/enp3s0/100/forwarding' to '1' Failed to write '1' to '/proc/sys/net/ipv4/conf/enp3s0/100/forwarding': No such file or directory Setting 'net/ipv4/conf/enp5s0/forwarding' to '1' # sysctl -p 99-sysctl.conf net.ipv4.conf.enp3s0/200.proxy_arp_pvlan = 1 net.ipv4.conf.enp3s0/200.forwarding = 1 net.ipv4.conf.enp3s0/100.forwarding = 1 net.ipv4.conf.enp5s0.forwarding = 1
AFAICT, sysctl replaces '.' with '/', and '/' with '.'. So it'll write /proc/sys/net/ipv4/conf/enp3s0.200/forwarding Do you have a file with a dot in the name?
it's posted as the first section in my report.
Where exactly?
# cat 99-sysctl.conf net.ipv4.conf.enp3s0/200.proxy_arp_pvlan=1 net.ipv4.conf.enp3s0/200.forwarding=1 net.ipv4.conf.enp3s0/100.forwarding=1 net.ipv4.conf.enp5s0.forwarding=1 sysctl -p /etc/sysctl.d/99-sysctl.conf will parse this correctly. systemd-sysctl will not parse the first three lines correctly.
> net.ipv4.conf.enp3s0/200.proxy_arp_pvlan=1 The question is how is the *file* that sysctl writes to called?
exactly opposite the conf file syntax. e.g.: /proc/sys/net/ipv4/conf/enp3s0.200/proxy_arp_pvlan
So you are saying that the classic sysctl tool actually maps "." to "/" and "/" to "." in the fs? How incredibly awful.
i'll agree, it turned out to be awkward, but it's the standard we've had for two decades :}
Fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=2e573fc.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.