Turd Ferguson wrote:
I'm not quite sure what you mean.
/dev/eth0 is the interface that goes to my ISP /dev/eth1 is the interface that goes to my internal network
According to the output, that is how it is, right?
FW_DEV_EXT="eth0" - External Interface FW_DEV_INT="eth1" - Internal Interface
FW_MASQ_DEV="FW_DEV_EXT" as is correct per the documentation.
Am I misunderstanding you?
Set this line: FW_PROTECT_FROM_INTERNAL="yes" to FW_PROTECT_FROM_INTERNAL="no" and test it again. De computer with the firewall functions now as a DMZ machine, I think... Your internal network is also looking at a firewall. With the option changed, the firewall for the internal network is down. Now only a external firewall. This should work..... If you need a firewall for the internal network, you should dig some more in de docs. Because I have no experience with it.
</Jared>
On Thu, 2003-03-27 at 01:07, Togan Muftuoglu wrote:
* Turd Ferguson; <turdferguson@infowest.com> on 27 Mar, 2003 wrote:
Nope, I lied...I the firewall was still in test mode.
Here the log copy: Mar 27 00:48:15 gatekeeper kernel: SuSE-FW-ACCESS_DENIED_INT IN=eth1
^^^^^^^^
Interesting you were saying your external is "eth0" but looks like here "eth1" is the incoming interface
--
Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
-- -- Thanks in advance, Stefan -------------------------------------------------------------- Linux a world without borders, fences, windows and gates..... Titanic98 "Which computer do you want to sink today????"