Hi, all, Last week there was talk on the list of some poor soul who set up his firewall and nothing could get through at all. This happened to me too. I went to the archives and saw that the last message I could find said, Date: Fri, 19 Apr 2002 15:14:08 +0300 From: Togan Muftuoglu <toganm@dinamizm.com> Message-ID: <20020419151408.A2054@dinamizm.com> Subject: Re: [SLE] Nothing will pass through firewall2 * steve; <fsanta@arrakis.es> on 19 Apr, 2002 wrote:
Still nothing. Thanks for the suggestions from Togan and Joost, I have included them in the latest setup below.
FW_MASQUERADE="no"
Try with yes
Also start the firewall with "/sbin/SuSEfirewall2 test " and then get the firewall log and search for DROP rules anything that is related to trying out to going to websites on the net but has been logged as DROP could be aproblem area
Ah. Okay,I did that and it started with the warning: Warning: SuSEfirewall2 is running in TEST MODE, no packet filtering is done! Warning: detected activated samba, enabling FW_SERVICE_SMB! You still have to allow tcp port 139 on internal, dmz and/or external. To which i say...HUH?? No packet filtering done.. Does that mean the firewall's up and not doing anything? And still having to allow tcp port 139 ... could that be the problem I was having earlier when nothing got out - that I still had to allow etc. etc? Thanks in advance, NIck
* Nick Selby; <php@nickselby.com> on 08 May, 2002 wrote:
To which i say...HUH?? No packet filtering done.. Does that mean the firewall's up and not doing anything?
well it is not blocking anything however it logs the actions it would do normally so you can read the logs and decide where to tweak, hence is the name test
And still having to allow tcp port 139 ... could that be the problem I was having earlier when nothing got out - that I still had to allow etc. etc?
have you permit port 139 to internal in your firewall2.rc.config -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
participants (2)
-
Nick Selby -
Togan Muftuoglu