All of lore.kernel.org
 help / color / mirror / Atom feed
* nftables, after adding a rule without any action, nft doesn't return correctly
@ 2014-07-16 15:37 Ryo Fujita
  2014-07-16 16:07 ` Pablo Neira Ayuso
  2014-07-16 23:52 ` Alex van den Bogaerdt
  0 siblings, 2 replies; 7+ messages in thread
From: Ryo Fujita @ 2014-07-16 15:37 UTC (permalink / raw)
  To: netfilter

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?

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

My environment was as followings.
nftables-0.100-3.20140704git.fc21.x86_64
libnftnl-1.0.2-1.fc21.x86_64
kernel-3.15.4-200.fc20.x86_64

Best Rio.

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2014-07-18  0:49 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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.