> On Saturday, August 03, 2013 04:25:46 PM johnny bowen wrote: >> IP Forwarding is used when you need to send packets from one interface > to >> another. So if you're using Shorewall there's a good change you're doing >> this if you're using it as a firewall for a LAN. By default it's turned >> off >> on most Distrobutions. >> >> ip_forwarding is the kernel parameter that allows IP Forwarding. It's >> current value can be found in /proc: >> # cat /proc/sys/net/ipv4/ip_forward 0 is off; 1 is >> on >> >> There are several ways to turn in on: >> >> 1) # echo 1 > /proc/sys/net/ipv4/ip_forward >> >> 2) # sysctl -w net.ipv4.ip_forward=1 >> >> 3)# echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf && sysctl -p >> >> 4) add IP_FORWARDING=On to shorewall.conf and run shorewall restart > > You seem to be saying that setting IP_FORWARDING = On in shorewall.conf > and re-starting shorewall should change the setting of net.ipv4.ip_forward > . > This did not happen in my case. > I have "IP_FORWARDING=On" in shorewall.conf > and I re-started shorewall (several times) on my CentOS-6.4 server, > but "sudo sysctl net.ipv4.ip_forward" reported "net.ipv4.ip_forward = 0".
Hi, Do you have something else installed which could change forwarding (NetworkManager or something)? Could it be a problem with SELinux? Regards, Simon ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
