From: Brian Austin - Standard Universal <brian@standarduniversal.com.au>
To: Leonardo Carneiro <lscarneiro@veltrac.com.br>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Learning iptables
Date: Sat, 18 Apr 2009 22:48:42 +1000 [thread overview]
Message-ID: <49E9CC2A.3040506@standarduniversal.com.au> (raw)
In-Reply-To: <49E9C87A.1030509@veltrac.com.br>
Hi,
the only reason I would think is to allow packets through for the
milliseconds it takes the script to run.
regards
Brian
Leonardo Carneiro wrote:
> Hi everyone,
>
> I'm have a avarage-to-good linux knowlegde, but i'm quite noob when it
> comes about iptables, so i decided to study about.
> I'm reading a lot of articles and blogs, and testing some rules, so
> far it's all going well.
> Right now i'm running a server with tons of rules written by the admin
> that worked here before me, and in the policies session of the script
> i've found theses rules:
>
> $IPTABLES -P INPUT ACCEPT
> $IPTABLES -P OUTPUT ACCEPT
> $IPTABLES -P FORWARD ACCEPT
> $IPTABLES -F
> $IPTABLES -t nat -F
> $IPTABLES -t mangle -F
> $IPTABLES -X
>
> $IPTABLES -A INPUT -s $LO_IP -j ACCEPT
> $IPTABLES -A OUTPUT -d $LO_IP -j ACCEPT
> $IPTABLES -A INPUT -s $LAN_IP -j ACCEPT
> $IPTABLES -A OUTPUT -d $LAN_IP -j ACCEPT
> $IPTABLES -A INPUT -s $INET_IP_DIN -j ACCEPT
> $IPTABLES -A OUTPUT -d $INET_IP_DIN -j ACCEPT
>
> $IPTABLES -P INPUT DROP
> $IPTABLES -P OUTPUT ACCEPT
> $IPTABLES -P FORWARD DROP
>
> Is there any good reason why someone would set an ACCEPT policy for
> all chains first to withdraw some later? What the benefit of doing this?
>
> Sorry about my poor english.
>
> Tks in advance
next prev parent reply other threads:[~2009-04-18 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 12:32 Learning iptables Leonardo Carneiro
2009-04-18 12:48 ` Brian Austin - Standard Universal [this message]
2009-04-18 12:59 ` Thomas Jacob
2009-04-18 13:20 ` Leonardo Carneiro
2009-04-18 23:34 ` Amos Jeffries
2009-04-18 15:55 ` Bruno Moreira Guedes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E9CC2A.3040506@standarduniversal.com.au \
--to=brian@standarduniversal.com.au \
--cc=lscarneiro@veltrac.com.br \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.