All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 16 Jul 2014 18:07:16 +0200	[thread overview]
Message-ID: <20140716160716.GA7906@salvia> (raw)
In-Reply-To: <DA2F5FF8-CA37-48D0-BEFC-F1D78A0C8415@redhat.com>

On Thu, Jul 17, 2014 at 12:37:43AM +0900, Ryo Fujita wrote:
> Hi,
> 
> I’m still a newbie to nftables and couldn’t distinguish right behavior from a bug.
> 
> I found a weird behavior of nft command.
> 
> # nft -f /etc/nftables/inet-filter
> # nft add rule inet filter input log drop
> # nft add rule inet filter input ip saddr 192.168.1.21 // without any action like ‘drop’, ‘accept’, ‘log’ and so on
> # nft list chain inet filter input
> table inet filter {
> 	chain input {
> 		 type filter hook input priority 0;
> 		 log drop
> ^C << - - - - - - - break
> 
> I have 2 questions.
> 
> 1. Adding a rule without any action didn’t result any error. Was it correct behavior?

You can add rules without any action.

> 2. After adding a rule, nft didn’t return, needed to break, ^C. Was it a bug?

Try -n to disabling name resolution:

# nft -n list table inet filter

> 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

Thanks.

  reply	other threads:[~2014-07-16 16:07 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 [this message]
2014-07-16 23:13   ` Ryo Fujita
2014-07-17 14:14     ` Pablo Neira Ayuso
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=20140716160716.GA7906@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 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.