Red Hat Bugzilla – Bug 150753
FORWARD_IPV4 not used
Last modified: 2014-03-16 22:52:52 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: /usr/share/doc/initscripts-7.93.5/sysconfig.txt states that the FORWARD_IPV4 option is still valid in /etc/sysconfig/network for turning on IPv4 forwarding. However, the option does not appear to work and none of the network scripts seem to look for it. Even worse, the /etc/rc.d/init.d/network script disables IPv4 forwarding on stop, so restarting the network will disable forwarding which was turned on by another means (e.g. set in /etc/sysctl.conf or otherwise). Version-Release number of selected component (if applicable): initscripts-7.93.5-1 How reproducible: Always Steps to Reproduce: 1. Set FORWARD_IPV4=yes 2. Start network 3. Note that forwarding is still disabled despite (1) 4. sysctl -w net.ipv4.ip_forward=1 5. Note that forwarding is now on 6. /etc/rc.d/init.d/network restart 7. Note that forwarding has now been turned off again despite the option (1) Actual Results: IPv4 forwarding cannot be turned on by recommended means. Forcing it on manually by sysctl works but it turned off again upon network restart. Expected Results: FORWARD_IPV4=yes option should be honoured as documented. Infact I think this should probably also be the default if FORWARD_IPV4=no is not specified. Additional info:
It's supposed to be enabled by editing sysctl.conf. In fact, if you look at the documentation: obsoleted values from earlier releases: FORWARD_IPV4=yes|no This setting has been moved into net.ipv4.ip_forward setting in /etc/sysctl.conf. Setting it to 1 there enables IP forwarding, setting it to 0 disables it (which is the default for RFC compliance).
*** Bug 150755 has been marked as a duplicate of this bug. ***
*** Bug 150754 has been marked as a duplicate of this bug. ***