From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Steve Horsley <steve.horsley@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables segv while trying to use nat redirection with map
Date: Tue, 3 Nov 2015 13:08:47 +0100 [thread overview]
Message-ID: <20151103120847.GA2559@salvia> (raw)
In-Reply-To: <5637F161.3090308@gmail.com>
On Mon, Nov 02, 2015 at 11:27:29PM +0000, Steve Horsley wrote:
> Sorry for the delay in answering.
>
> I installed the development version of Ubuntu 16.10 with proposed updates.
> With this version, nft -v reports version 0.5. My original set of commands
> now works without crashing, so thanks for the advice to try version 0.5.
>
> However, this set of commands still fails:
>
> # nft flush ruleset
> # nft add table nat
> # nft add chain nat output { type nat hook output priority 0 \; }
> # nft add map nat outnat {type ipv4_addr : ipv4_addr\; }
> # nft add element nat outnat { 172.16.1.1 : 8.8.8.8 , 172.16.1.2 : 8.8.4.4 }
> # nft add rule ip nat output dnat ip daddr map @outnat
> <cmdline>:1:1-48: Error: Could not process rule: Invalid argument
> add rule ip nat output dnat ip daddr map @outnat
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> It looks as though I have a syntax error in the command, but I can't find a
> good example to use as a template. Do I have the syntax wrong, or is using a
> separate set like this not possible?
This is working here. What kernel version are you using?
This problem is resolved in 4.2.4 and it should be in 4.1.12 too.
next prev parent reply other threads:[~2015-11-03 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 12:32 nftables segv while trying to use nat redirection with map Steve Horsley
2015-10-18 18:00 ` Pablo Neira Ayuso
2015-11-02 23:27 ` Steve Horsley
2015-11-03 12:08 ` Pablo Neira Ayuso [this message]
2015-11-03 18:24 ` Steve Horsley
2015-11-03 19:39 ` Arturo Borrero Gonzalez
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=20151103120847.GA2559@salvia \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=steve.horsley@gmail.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