I am using the version that comes with SuSE 7.0, firewals-2.6-10. I
have FW_FORWARD_TCP="192.168.0.0/16,172.20.10.0/24,ssh". 192.168.0.0
is the range of the internal networks, 172.20.10.0/24 is the subnet
for the DMZ. The DMZ was moved out of my back bedroom last week,
to my employer's new office, so I am relying on the backup copies of
files and hoping nothing significant has changed.
HTH,
Jeffrey
Quoting Konstantin (Kastus) Shchuka
On Sun, Feb 25, 2001 at 08:52:32PM -0600, Jeffrey Taylor wrote: [snip] I've tried this (maybe a bit modified). There are neither COUNTER nor IPMASQADM variables in SuSEfirewall script. So I ran ipchains and ipmasqadm commands manually after starting rcfirewal. No good, nothing gets forwarded. ``ipmasqadm mfw -L'' shows correct results for the IP and port.
I checked, I can access Apache on internal NT from firewal machine, but if I try to access it from outside, connection never opens.
What version of firewals do you use? Do you set any values to FW_FORWARD_TCP in configuration file? What else may be different in my setup from yours?
Thanks, -Kastus
Quoting Konstantin (Kastus) Shchuka
: Hi there,
Has anybody on the list got any success configuring port forwarding using firewals-2.1-5.rpm?
I am driven completely mad. I followed all comments in configuration file, I looked thoroughly through examples, -- to no avail!
I also tried ipmasqadm with mfw module--no good.
What I actually need to do:
I have SuSE 6.4 box as a firewall. I have an NT box on internal network. I need to make Apache running on NT visible from the Internet.
Pretty simple, you would say. I thought it too. It appeared not so simple.
Please help.
-Kastus
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck