OK, I got the message!
I'll read the fine manual first.
But what I tried to say is that I did configure SuSEfirewall2, and that I
did get some response back, but that I did not got the idea it was doing
what i've just configured.
After some investigation (and help from this list) I found that using WebMin
for configuring the SuSE firewall isn't doing the whole job. Using the
command iptables -L -v -n|grep -v "^ *0 " showed a lot more than that I got
presented from the Webmin screen.
So what did I learn today? Stop using 'simple' management tools!
Thanks for your help.
----- Original Message -----
From: "Carlos E. R."
The Sunday 2005-04-03 at 22:08 +0200, Guus Teley RI wrote:
I'm really lost at the SuSE firewall 2.
As far as I can see, the ONLY firewall in place is the SuSE firewall, but it doesn't seem to matter what rules I configure, it keeps blocking those ports I thought I'd just opened.
It is "SuSEfirewall2" now.
You should give details so that people can comment.
I recently upgraded from 8.2 to 9.2 I did not see any errors, but did notice that the default KDE login screen keeps saying 8.2 instead of 9.2.
You'd better ask this on the suse-linux-e list.
¿Do you have more than one partition fo rlinux, per chance?
-- Cheers, Carlos Robinson
-- 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