I am having a strange problem on Fedora 16. I am trying to figure out what is going on, but have not yet been successful.
I am using Xen with routed interfaces instead of bridged (i.e., vif-script vif-route). In this case, the "network-route" script should enable kernel port forwarding. However, this is not the case---at least the first time xend runs. Xend runs, but /proc/sys/net/ipv4/ip_forward still contains "0".
But, if I restart xend by hand using "service xend restart", then kernel IP forwarding gets turned on.
At first I thought this may be due to SELinux (perhaps systemd starts xend in a different context than a root shell does). But this is not the case; I get the same behavior when I boot with SELinux in permissive mode.
Does anyone else know what might be causing this?
On Tue, 15 Nov 2011 14:09:31 -0600 W. Michael Petullo wrote:
Does anyone else know what might be causing this?
I have lots of problems with random "network stuff" not working at boot now that systemd is starting everything. I've taken to putting lines like this in /etc/rc.d/rc.local
/bin/bash -c 'sleep 5 ; service ypbind restart' > /dev/null 2>&1 < /dev/null & /bin/bash -c 'sleep 10 ; service nscd restart' > /dev/null 2>&1 < /dev/null &