|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: [suse-security] DMZ egress access problem
From: Arjen Runsink (arjen
zeilers.net)
Date: Thu May 22 2003 - 03:23:32 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello Maarten
Quoting maarten van den Berg <maarten
vbvb.nl>:
> FW_MASQ_DEV="eth0 eth2"
Hmm, I don't think it is necessary to masquerade on eth2, and just maybe
that is the culprit
> FW_FORWARD="0/0,X.Y.Z.160/28,tcp,80 0/0,X.Y.Z.160/28,tcp,22
> X.Y.Z.160/28,0/0"
This syntax looks correct indeed.
So remove eth2 from FW_MASQ_DEV and the forward rule from dmz to
outside, because I think the fw rules that are setup already should
allow this.
If this does not work have a good look at the routing table on the fw
Als the DMZ if should be the default gw for the servers in the DMZ
BB, Arjen
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help
suse.com
Security-related bug reports go to security
suse.de, not here
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]