From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [ANNOUNCE]: First release of nftables
Date: Wed, 18 Mar 2009 09:28:03 +0100 [thread overview]
Message-ID: <49C0B093.7000908@trash.net> (raw)
In-Reply-To: <49C078B6.4020603@trash.net>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
Patrick McHardy wrote:
> Examples
The rule snippets under tests/ pretty much all use obsolete syntax,
so I'm attaching a test script (which doesn't make much sense, just
testing features) so people can get a feeling for the syntax.
[-- Attachment #2: test --]
[-- Type: text/plain, Size: 1499 bytes --]
#! /home/kaber/src/nf/nft/nftables/src/nft -nf
#include "ipv4-filter"
flush table filter
delete table filter
table filter {
chain log_drop {
counter log prefix "drop" drop
}
chain log_accept {
counter log prefix "accept" accept
}
chain accept_related {
counter
tcp dport < 1024 counter log prefix "drop-related" drop
udp dport < 1024 counter log prefix "drop-related" drop
ct helper "sip" counter log prefix "accept-related-sip" accept
ct helper "ftp" counter log prefix "accept-related-ftp" accept
ct helper "irc" counter log prefix "accept-related-irc" accept
counter log prefix "accept-related" accept
}
chain accept_stateful {
counter
ct state vmap { established => accept, related => jump accept_related }
counter
}
chain input_local {
counter
jump accept_stateful
jump log_accept
}
chain output_local {
counter
jump accept_stateful
udp dport { 123, 631, 514} accept
jump log_accept
}
chain input {
hook NF_INET_LOCAL_IN 0
counter
meta iif vmap { \
"eth0" => jump input_local, \
"eth1" => jump input_local, \
* => continue, \
}
counter
}
chain test1 {
counter
}
chain output {
hook NF_INET_LOCAL_OUT 0
counter
meta oif vmap { \
"eth0" => jump output_local, \
"eth1" => jump output_local, \
* => continue, \
} counter
meta oif { \
"eth0", \
"eth1", \
} counter
ip daddr vmap { \
192.168.0.1 => jump test1, \
* => continue, \
} counter
}
}
next prev parent reply other threads:[~2009-03-18 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 4:29 [ANNOUNCE]: First release of nftables Patrick McHardy
2009-03-18 8:13 ` Jan Engelhardt
2009-03-18 8:21 ` Patrick McHardy
2009-03-18 8:28 ` Patrick McHardy [this message]
[not found] ` <20090318092039.GA2511@squirrel.roonstrasse.net>
2009-03-18 9:52 ` Patrick McHardy
2009-03-18 9:58 ` Andi Kleen
2009-03-18 10:04 ` Patrick McHardy
2009-03-18 10:13 ` Varun Chandramohan
2009-03-18 10:17 ` Patrick McHardy
[not found] <20090318112937.675BF13A4B0@koiott.tartu-labor>
2009-03-18 12:00 ` Meelis Roos
2009-03-18 14:39 ` Patrick McHardy
2009-03-18 14:52 ` Denys Fedoryschenko
2009-03-18 14:58 ` 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=49C0B093.7000908@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 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.