Should I disable netfilter, or just remove /etc/rc.firewall

mokele · 09-19-2006, 06:00 PM

I'm having a DHT Firewalled in azureus. I'm trying to
eliminate all posibilities of firewall software executing.

Not sure if I by removing /etc/rc.firewall would be
enough, or do I have to disable netfilter in the kernel...

I have:
.Ports on Linksys router needed for TCP/UDP opened
.Ports on 2Wire router neeeded for TCP/UDP opened
.Azureus removed/reinstalled

mokele · 09-20-2006, 06:29 AM

Anyone? ... Please ...

unSpawn · 09-20-2006, 06:33 AM

You better find out which ports it blocks instead of opening up your box to teh intarweb.

mokele · 09-20-2006, 04:33 PM

thanks.

You mean, I shouldn't remove iptables. Instead I
should configure it. ...?

win32sux · 09-20-2006, 07:14 PM

Quote:

Originally Posted by mokele

thanks.

You mean, I shouldn't remove iptables. Instead I
should configure it. ...?

yes, i'm pretty sure that's what he means... even if you have a router and stuff, having your iptables properly configured locally is always a good idea... that said, if you wanna disable your firewall on slackware, you don't need to delete your rc.firewall (or make any changes to the kernel) - you basically just need to make it non-executable, like:

Code:

chmod a-x /etc/rc.d/rc.firewall

then upon reboot, your firewall will be disabled (no rules and all policies set to ACCEPT)... if you wanna reset your firewall without having to reboot after doing the chmod, run this script:

Code:

#!/bin/sh

IPT="/usr/sbin/iptables"

$IPT -P INPUT ACCEPT
$IPT -P OUTPUT ACCEPT
$IPT -P FORWARD ACCEPT

$IPT -t mangle -P PREROUTING ACCEPT
$IPT -t mangle -P INPUT ACCEPT
$IPT -t mangle -P FORWARD ACCEPT
$IPT -t mangle -P OUTPUT ACCEPT
$IPT -t mangle -P POSTROUTING ACCEPT

$IPT -t nat -P PREROUTING ACCEPT
$IPT -t nat -P POSTROUTING ACCEPT
$IPT -t nat -P OUTPUT ACCEPT

$IPT -F
$IPT -F -t nat
$IPT -F -t mangle

$IPT -X
$IPT -X -t nat
$IPT -X -t mangle

remember that running without a firewall is a very bad idea!!!

my suggestion would be that you post your rc.firewall and see if you can get some feedback on what you need to do in order for your software to work properly...

mokele · 09-20-2006, 08:47 PM

hmmm...Very good info win32sux.

Looking at what you posted I noticed rc.firewall located
at /etc/rc.d/

Now I'm realizing that may be I've never had iptables
configured, not even for a basic protection because
I don't have an rc.firewall in /etc/rc.d/

I installed guarddog just to try configuring something
on my slack box from GUI for the first time. I just
don't get use to it. I think I'm going to try learning
this like every other stuff; CLI.

Now. Something I learned from the little I did with
guarddog is that rc.firewall is stored at /etc/

Is this a soft link to /etc/rc.d/rc.firewall?, Or is
it the location guarddog uses?

Anyways I have a lot of reading to do I'll post the outcome

-W

win32sux · 09-20-2006, 08:52 PM

not sure about guarddog's location preference... all i know is that the slackware startup scripts will look for /etc/rc.d/rc.firewall by default...

to check your current/active firewall rules just do a (as root):

Code:

iptables -L -v -n

post the output if you want...

by running this command you can be sure of exactly what your firewall is currently doing...

mokele · 09-20-2006, 09:07 PM

Code:

Chain INPUT (policy ACCEPT 115K packets, 9862K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 158K packets, 188M bytes)
 pkts bytes target     prot opt in     out     source               destination

That's the output win32sux. Correct me on this one
I just want to know if I understand your suggested
command output.

It means I have something like a DMZ?

win32sux · 09-20-2006, 09:09 PM

Quote:

Originally Posted by mokele

Code:

Chain INPUT (policy ACCEPT 115K packets, 9862K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 158K packets, 188M bytes)
 pkts bytes target     prot opt in     out     source               destination

That's the output win32sux. Correct me on this one
I just want to know if I understand your suggested
command output.

It means I have something like a DMZ?

it means your box doesn't have any firewall rules running on it... you aren't filtering any packets - everything is being allowed in and out... =/

you can rest assured the issue isn't caused by the local firewall... it has to be something else... your router perhaps?? software configuration?? not sure...

mokele · 09-20-2006, 09:26 PM

Right. But now I'm worried with a bigger concern.
-iptables- I'm betting my 2 bucks on the application.
It wasn't doing this before and I havent change anything
in my routers config. About a week ago that little problem
started. Anyways now I'm more interested in solving my
iptables issue. I have something new to learn.

Thank you!! very much win.

-W

win32sux · 09-20-2006, 09:46 PM

Quote:

Originally Posted by mokele

Right. But now I'm worried with a bigger concern.
-iptables- I'm betting my 2 bucks on the application.
It wasn't doing this before and I havent change anything
in my routers config. About a week ago that little problem
started. Anyways now I'm more interested in solving my
iptables issue. I have something new to learn.

Thank you!! very much win.

-W

cool... if you have any question about iptables just ask... i'll gladly help you with whatever i can... good luck...