From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Harsha Sharma <harshasharmaiitr@gmail.com>
Cc: netfilter-devel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: nftables: Add support for unsupported codes in icmp and icmp6 extensions
Date: Wed, 4 Oct 2017 13:08:52 +0200 [thread overview]
Message-ID: <20171004110852.GA2575@salvia> (raw)
In-Reply-To: <1507110760.6328.16.camel@harryPotter>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
Hi Harsha,
I would suggest you start with a more simple task:
Probably you can add one test for named objects to our tests/shell/
directory under nftables.git tree.
I'm attaching a couple of examples. Please, have a look at
nft/tests/shell/ directory.
Thanks.
[-- Attachment #2: nft-limit-name --]
[-- Type: text/plain, Size: 284 bytes --]
table ip filter {
limit http-traffic {
rate 1/second
}
chain input {
type filter hook input priority 0; policy accept;
limit name tcp dport map { 80 : "http-traffic", 443 : "http-traffic"}
}
}
[-- Attachment #3: nft-stateful-objs --]
[-- Type: text/plain, Size: 686 bytes --]
table ip x {
counter user123 {
packets 12 bytes 1433
}
quota user123 {
over 2000 bytes
}
quota user124 {
over 2000 bytes
}
set y {
type ipv4_addr
}
map test {
type ipv4_addr : quota
elements = { 192.168.2.2 : "user124", 192.168.2.3 : "user124"}
}
chain y {
type filter hook input priority 0; policy accept;
counter name ip saddr map { 192.168.2.2 : "user123", 1.1.1.1 : "user123", 2.2.2.2 : "user123"}
quota name ip saddr map @test drop
}
}
prev parent reply other threads:[~2017-10-04 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 9:52 nftables: Add support for unsupported codes in icmp and icmp6 extensions Harsha Sharma
2017-10-04 11:08 ` Pablo Neira Ayuso [this message]
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=20171004110852.GA2575@salvia \
--to=pablo@netfilter.org \
--cc=harshasharmaiitr@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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;
as well as URLs for NNTP newsgroup(s).