Am 16.06.2013 23:58, schrieb Ross Lagerwall: >> The problem Zbigniew describes is that if one adds config options with >> predictable network names used, and we do not apply the stuff at >> "move", we will never apply them. >> > OK, thanks. But my testing shows otherwise: I created a .conf file with: > net.ipv4.conf.enp1s0.forwarding=1 > (where eth0 is the old name, enp1s0 is the new, predictable name) > It *correctly* sets /proc/sys/net/ipv4/conf/enp1s0/forwarding=1 after > a reboot with the patch applied. > > I'm still not clear about in which situations it could fail?
and because all this magic is too fragile at least since Fedora 18 i created a service which is started after network.service and since them all my services and forwardings are working again as expected [root@srv-rhsoft:~]$ cat /etc/systemd/system/sysctl-post-network.service [Unit] Description=apply settings after network After=network.service openvpn.service hostapd.service network-wlan-bridge.service [Service] Type=oneshot RemainAfterExit=yes ExecStart=/usr/sbin/sysctl -p StandardOutput=null [Install] WantedBy=multi-user.target
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
