http://qa.mandrakesoft.com/show_bug.cgi?id=514
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2003-29-07 21:34 -------
This fix may work for the bug mentioned, but removing the sysctl call results in
device-specific sysctl options not being available.
Please see this MandrakeClub post for an example of the problem:
http://www.mandrakeclub.com/modules.php?op=modload&name=Splatt_Forum&file=viewtopic&topic=10027&forum=11
Maybe a better solution is to migrate the IPV4 settings into /etc/sysctl.conf ?
Either way, the config tool (ie drakconnect) should prune deprecated settings
from the config files.
--
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.
