http://bugzilla.suse.com/show_bug.cgi?id=572202
http://bugzilla.suse.com/show_bug.cgi?id=572202#c22
--- Comment #22 from Matthias Gerstner ---
New maintainer for SuSEfirewall2 here.
Starting with the oldest pending bug first. This one just had its 7 year
anniversary ;-)
I've reviewed the current state of affairs and as it looks yast2-network is by
now setting up IPv4 and IPv6 forwarding on its own. This was discussed and
fixed in bug 916013.
For IPv4 we're now in an unfortunate situation:
- in SuSEfirewall2 the configuration variable FW_ROUTE is expected to enable
IPv4 forwarding, what it currently does, even if IPv4 forwarding is not
enabled in yast2-network, by directly writing to /proc.
- in yast2-network IPv4 forwarding is enabled implicitly via SuSEfirewall2, if
it is enabled, by setting FW_ROUTE=yes, otherwise via sysctl. IPv6
forwarding is exclusively configured via sysctl.
That yast configures IPv4 forwarding differently depending on whether
SuSEfirewall2 is enabled or not is somewhat unexpected. I'd like to remove the
IPv4 forwarding configuration completely from SuSEfirewall2, but this would
easily break routing configurations and the working together with yast.
Any thoughts on this?
--
You are receiving this mail because:
You are on the CC list for the bug.