I have been having problems getting a firewall addition to work (Firestarter). I thought that I would start afresh and did a search for Firestarter and removed all found directories and files. On re installing it I could not get it to work properly. Took it out again and checked the basic Suse Firewall 2 which does not seem to be working. Shields Up shows port 139 wide open. I then took out Suse f/w 1 & 2, put them back. No difference. Took them out again, also iptables, ipchains. Put them all back. Still no difference. I did reboot between these to make sure. I notice that if in rc-config I put fw=yes, then on the boot up log, I see firewall stage 1 of 3 ok, stage 2 of 3 failed. The only alternative I can think of is to re install Suse 7.2 again. Any one got any ideas please, before I have to commit to this again. Regards, David
* David;
I thought that I would start afresh and did a search for Firestarter and removed all found directories and files. On re installing it I could not get it to work properly. Took it out again and checked the basic Suse Firewall 2 which does not seem to be working. Shields Up shows port 139 wide open.
Well in the firewall.rc.config thereis part regarding samba check that try with yes /no Option 2 is thereis firewall.custom.rc.config you can hardcode your DROP rule for 139 HTH -- Togan Muftuoglu
Thanks Togan On Mon, 3 Dec 2001 17:03:44 +0200, Togan Muftuoglu wrote:
Well in the firewall.rc.config thereis part regarding samba check that try with yes /no
Yes I have done that, but it doesn't change anything
Option 2 is thereis firewall.custom.rc.config you can hardcode your DROP rule for 139
It's not only 139. I checked the other ports and most are open, the few others are only closed. I think the firewall is broken. Can't see how to get it together again without re installing Suse. Regards, David
participants (2)
-
David
-
Togan Muftuoglu