From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: why do we need to allow all traffic from lo interface???
Date: Tue, 29 Oct 2002 08:52:23 +0000 [thread overview]
Message-ID: <20021029085225.FVET1554.mta07-svc.ntlworld.com@there> (raw)
In-Reply-To: <F44M0DopbFQffqlRxqf000167c0@hotmail.com>
On Tuesday 29 October 2002 1:09 am, Tan Ming Han wrote:
> hi,
> I seen some examples allowing all traffic (in INPUT and OUTPUT) from lo
> interface. Why is it so? Is it becos of the local XWindow connection?
X requires this, yes; there are also certain other applications which use
things like rpc calls or ident lookups. A simple way to find out what
traffic goes across the lo interface is to log it for a while:
iptables -A INPUT -i lo -j LOG --log-prefix="In-lo: "
iptables -A INPUT -i lo -j ACCEPT
Antony.
--
Windows: just another pane in the glass.
next prev parent reply other threads:[~2002-10-29 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 1:09 why do we need to allow all traffic from lo interface??? Tan Ming Han
2002-10-29 8:52 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 10:00 Ben Tan
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=20021029085225.FVET1554.mta07-svc.ntlworld.com@there \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox