OK, I did an: 'iptables --flush INPUT' 'iptables --flush FORWARD' 'iptables --flush OUTPUT' It removed the firewall related errors. Thanks for the tip. --- Jeff Lanzarotta wrote:

The output of 'iptables -L -n' is:

--------8<--------

Chain INPUT (policy ACCEPT) target prot opt source destination LOG 0 -- 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 7 prefix `BANDWIDTH_IN:'

Chain FORWARD (policy ACCEPT) target prot opt source destination LOG 0 -- 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 7 prefix `BANDWIDTH_OUT:' LOG 0 -- 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 7 prefix `BANDWIDTH_IN:'

Chain OUTPUT (policy ACCEPT) target prot opt source destination LOG 0 -- 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 7 prefix `BANDWIDTH_OUT:'

--------8<--------

I have noticed a files in the /var/log directory named bandwidth and firewall. So I am assuming something is running, I just do not know what...

--- Darryl Gregorash wrote:

...

On 2007-04-17 14:05, Jeff Lanzarotta wrote:

...

Hello,

I am receiving,

------ Another Firewall Active Another kind of firewall is active in your system. If you continue, SuSEfirewall2 may produce undefined errors. It would be better to remove the other firewall before configuring SuSEfirewall2. ------

from yast when I attempt to configure SuSEfirewall2.

I have looked all over the system and I can not find what it is talking about. Could someone please shed some light on this...

What is the output of

iptables --L -n

-- Moral indignation is jealousy with a halo. -- HG Wells

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ha, good question... This issue is actually on a friend of mine's PC. I am trying to help him out as he is a very novice Linux user. So with that, there is no telling why these were set. :) I am curious as to how these actually got set in the first place. If I get a chance, I will peruse the log files and see what I can find. Again, thanks for the tip... --- Darryl Gregorash wrote:

...

OK, I did an: 'iptables --flush INPUT' 'iptables --flush FORWARD' 'iptables --flush OUTPUT'

It removed the firewall related errors.

Thanks for the tip. That begs the question, what created those iptables entries in the first

On 2007-04-18 11:07, Jeff Lanzarotta wrote: place? You may be able to answer that by looking at the various logfiles, the syslog config file (which by default in SuSELinux is syslog-ng), and perhaps by examining the boot scripts (use grep, for example, to check for the text BANDWIDTH_OUT, etc, case sensitive).

-- Moral indignation is jealousy with a halo. -- HG Wells

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org