https://qa.mandrakesoft.com/show_bug.cgi?id=514

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From [EMAIL PROTECTED]  2002-12-26 22:34 -------
 But it is not backward compatible. If FORWARD_IP4 is set it does NOT 
 set the ip forwarding.  The /etc/rc.d/init.d/network script is badly written. 
 
Although there is text in that script to set ip forwarding if the FORWARD_IPV4 
variable is set as true, that action is completely canceled by the sysctl 
stuff. It is ONLY the state of the net.ipv4.ip_forward variable which 
determines the state of the forwarding. 
 
Also, to state that a change like this is documented in an obscure file sounds 
like a bureaucrat. This change should be documented in the 
/etc/sysconfig/network file.  
 
 



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
description: 
It used to be ( Mandrake 8.2 and earlier) that IP forwarding was set  
up using  
FORWARD_IPV4=yes 
in /etc/sysconfig/network.  
Sudenly in 9.0 there are two places in which you must set it up, namely in 
/etc/sysconfig/network AND in /etc/sysctl.conf. This change is both immensely 
confusing, and inconsistant.  
The nnew sysctl.conf file is very unreadable by humans-- the old way at least 
meant users had a chance to understand what was happening.  
While it may be that there is some Drak type program somewhere which sets up 
both of these variables properly, I have not found it, nor is it  
clear as to what is happening. 
 
Why have you kept the /etc/sysconfig/network file for some of the setup 
variables, and moved others to a new obscure location (sysctl.conf)? 
 
I have now wasted an hour trying to figure out why ip forwarding was not being 
switched on, and I am sure others have the same problem. 
 
PS, this is with initscripts 6.91.10mdk, not 6.91.6mdk which is the highest 
number listed on your bug report page.

Reply via email to