From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alex Chapman <ajchapman88@hotmail.co.uk>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: nftables multi-dimensional dictionaries
Date: Fri, 4 Sep 2015 16:44:21 +0200 [thread overview]
Message-ID: <20150904144421.GA3711@salvia> (raw)
In-Reply-To: <DUB109-W37CC9580BFB40296703618E1570@phx.gbl>
On Fri, Sep 04, 2015 at 02:32:31PM +0100, Alex Chapman wrote:
> Hi Pablo,
>
> Thanks for the response. Do I need kernel 4.2 to support this? I'm on 4.1 currently and the command below is erroring:
>
> # nft add rule ip firewall forward meta iif . meta oif vmap { eth0 . lo : jump test }
> <cmdline>:1:55-79: Error: Could not process rule: Invalid argument
> add rule ip firewall forward meta iif . meta oif vmap { eth0 . lo : jump test }
> ^^^^^^^^^^^^^^^^^^^^^^^^^
> <cmdline>:1:55-79: Error: Could not process rule: No such file or directory
> add rule ip firewall forward meta iif . meta oif vmap { eth0 . lo : jump test }
> ^^^^^^^^^^^^^^^^^^^^^^^^^
> <cmdline>:1:1-79: Error: Could not process rule: No such file or directory
> add rule ip firewall forward meta iif . meta oif vmap { eth0 . lo : jump test }
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> (table named firewall and both 'forward' and 'test' chains configured).
You need this oneliner fix:
http://git.kernel.org/cgit/linux/kernel/git/pablo/nf.git/commit/?id=bf798657eb5ba57552096843c315f096fdf9b715
It's on its way to 4.3-rc and will send to -stable 4.1 and 4.2 asap.
prev parent reply other threads:[~2015-09-04 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 9:17 nftables multi-dimensional dictionaries Alex Chapman
2015-09-03 16:35 ` Pablo Neira Ayuso
2015-09-04 13:32 ` Alex Chapman
2015-09-04 14:44 ` 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=20150904144421.GA3711@salvia \
--to=pablo@netfilter.org \
--cc=ajchapman88@hotmail.co.uk \
--cc=netfilter@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.