From: "Michal Kubeček" <mkubecek@suse.cz>
To: netfilter@vger.kernel.org
Cc: "U.Mutlu" <for-gmane@mutluit.com>
Subject: Re: [iptables] misleading print
Date: Mon, 05 Dec 2011 16:44:28 +0100 [thread overview]
Message-ID: <2026716.mRmHE8f3qx@dhcp91> (raw)
In-Reply-To: <jbinrb$2l7$1@dough.gmane.org>
On Monday 05 of December 2011 16:26EN, U.Mutlu wrote:
> I have in my script these statements:
> iptables -A INPUT -i lo -j ACCEPT
> iptables -A OUTPUT -o lo -j ACCEPT
>
> When doing "iptables -L -n" then the above gets shown as this:
> ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
>
> IMHO, this could easily be misinterpreted if one looks
> only at the iptables output, because the crucial info,
> ie. that it applies to the "lo" device only, is missing...
Output of "iptables -L" doesn't show -i and -o matches by default. If
you want to see them, use "-v" option.
Michal Kubeèek
next prev parent reply other threads:[~2011-12-05 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 15:26 [iptables] misleading print U.Mutlu
2011-12-05 15:44 ` Jan Engelhardt
2011-12-05 15:44 ` Michal Kubeček [this message]
2012-08-09 22:00 ` Jan Engelhardt
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=2026716.mRmHE8f3qx@dhcp91 \
--to=mkubecek@suse.cz \
--cc=for-gmane@mutluit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).