From: "Gáspár Lajos" <swifty@freemail.hu>
To: paddy joesoap <paddyjoesoap@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: comments about local loopback interface rule granularity
Date: Tue, 13 Mar 2012 16:17:58 +0100 [thread overview]
Message-ID: <4F5F6526.2020205@freemail.hu> (raw)
In-Reply-To: <CAMmbHwnH1YSW8vFJu2aoFSnY-vSDRS9KtGdhSe2G=tdyhGgmsg@mail.gmail.com>
Hi,
2012-03-13 15:28 keltezéssel, paddy joesoap írta:
> I often see the following:
>
> iptables -A INPUT -i lo -j ACCEPT
> iptables -A OUTPUT -o lo -j ACCEPT
>
> where a default DROP policy is applied to both INPUT and OUTPUT chains.
Just a side note.
I always use these rules because:
- I just enable something and deny everything else... (ACCEPT the
specified and DROP as the policy).
- I want my local services run "as fas as they can"... (I use the
rules above as the first rule in the chain. Be aware that you can use
the rules above in the raw, mangle and filter tables too..)
- I do not think that there is anything filterable on the "lo" interface.
Swifty
prev parent reply other threads:[~2012-03-13 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 14:28 comments about local loopback interface rule granularity paddy joesoap
2012-03-13 15:06 ` Jan Engelhardt
2012-03-13 15:11 ` /dev/rob0
2012-03-13 15:17 ` Gáspár Lajos [this message]
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=4F5F6526.2020205@freemail.hu \
--to=swifty@freemail.hu \
--cc=netfilter@vger.kernel.org \
--cc=paddyjoesoap@gmail.com \
/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.