From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ryo Fujita <rfujita@redhat.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables, after adding a rule without any action, nft doesn't return correctly
Date: Thu, 17 Jul 2014 16:14:28 +0200 [thread overview]
Message-ID: <20140717141428.GA4063@salvia> (raw)
In-Reply-To: <9D590D9F-92DE-4832-8382-54E3C42BA881@redhat.com>
On Thu, Jul 17, 2014 at 08:13:12AM +0900, Ryo Fujita wrote:
> Hi Pablo-san and all,
>
> Thank you so much!
> You made me clear.
>
> > You can add rules without any action.
>
> I understand it’s the spec not a bug.
>
> > Try -n to disabling name resolution:
> >
> > # nft -n list table inet filter
>
>
> Yes, I check that reverse lookup fails as you pointed out.
>
> >> My environment was as followings.
> >> nftables-0.100-3.20140704git.fc21.x86_64
> >
> > Please, use latest when testing.
> >
> > http://www.netfilter.org/projects/nftables/downloads.html
>
>
> The reason why I’m using the slight old version is to write a
> magazine article introducing nftables. It’s easy for readers to
> install the version I checked with RPM or archive like
> 'nftables-0.3’. Anyway, I’ll test the latest before sending a
> report to this ML.
Not a good idea to stick to old versions. We're still changing syntax
in some aspects and resolving bugs at this stage. The user document
aims to be in sync with latest. You should recommend people to stick
to latest until 1.0 comes out.
next prev parent reply other threads:[~2014-07-17 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 15:37 nftables, after adding a rule without any action, nft doesn't return correctly Ryo Fujita
2014-07-16 16:07 ` Pablo Neira Ayuso
2014-07-16 23:13 ` Ryo Fujita
2014-07-17 14:14 ` Pablo Neira Ayuso [this message]
2014-07-18 0:49 ` Ryo Fujita
2014-07-16 23:52 ` Alex van den Bogaerdt
2014-07-17 5:22 ` Alex van den Bogaerdt
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=20140717141428.GA4063@salvia \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=rfujita@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox