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





------- Additional Comments From [EMAIL PROTECTED]  2003-31-07 04:00 -------
One proposed solution for setting interface-specific parameters is to create
interface-specific configuration files like "param-dummy0" at 

/etc/init.d/network-scripts/

The content of param-dummy0 would be:

hidden=1

or even something that can directly serve as a config file for sysctl:

net.ipv4.conf.dummy0.hidden=1

I don't know how to get the /etc/init.d/network script to make use of this new
configuration file, apart from running sysctl a second time and adopting the
second method above with a syntax similar to /etc/sysctl.conf. 

Thanks to MandrakeClub member michel.digirati for pointing out this problem and
also this possible workaround.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- 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]
status: REOPENED
creation_date: 
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