From: Patrick McHardy <kaber@trash.net>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [nft] the -nnn switch
Date: Fri, 19 Sep 2014 13:25:06 +0200 [thread overview]
Message-ID: <20140919112505.GA1158@acer.localdomain> (raw)
In-Reply-To: <CAOkSjBgOpbJmOXEX=a1kPXqDMs673ZTfB_Qg=q4V5L2JTsg77g@mail.gmail.com>
On Fri, Sep 19, 2014 at 11:49:02AM +0200, Arturo Borrero Gonzalez wrote:
> Hi,
>
> the -nnn switch in in nftables is IMO a bit annoying.
> We are bounded to use that switch in every serious usage of nft.
>
> Let me remember the current behaviour:
>
> -n -> don't translate IP addresses to names.
> -nn -> also, don't translate gids/uids to names.
> -nnn -> also, don't translate port numbers to names.
> default -> translate all numbers to names.
>
> I propose here that before nftables goes absolutely mainstream we
> change the behaviour to the opposite:
>
> -n -> translate IP addresses to names.
> -nn -> translate gids/uids to names.
> -nnn -> translate port numbers to names.
> default -> show all numerically.
>
> What do you think?
That seems quite counter intuitive. I'd say the default should be not
to cause any network traffic for a regular system (not using LDAP or
whatever), which would be -n. So I would be fine with -n being the
default and adding an option to also translate hostnames.
next prev parent reply other threads:[~2014-09-19 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 9:49 [nft] the -nnn switch Arturo Borrero Gonzalez
2014-09-19 11:25 ` Patrick McHardy [this message]
2014-09-22 9:54 ` Arturo Borrero Gonzalez
2014-09-22 10:04 ` Patrick McHardy
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=20140919112505.GA1158@acer.localdomain \
--to=kaber@trash.net \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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;
as well as URLs for NNTP newsgroup(s).