From: Eric Leblond <eric@regit.org>
To: Alex Chapman <ajchapman88@hotmail.co.uk>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: nftables jump <chain> target invalid argument
Date: Fri, 15 Nov 2013 14:06:50 +0100 [thread overview]
Message-ID: <1384520810.5425.2.camel@tiger2> (raw)
In-Reply-To: <DUB109-W87FE1E5161E5C42ED6593AE1F80@phx.gbl>
Hello,
On Thu, 2013-11-14 at 16:53 +0000, Alex Chapman wrote:
> Hi,
>
> When attempting to use the jump target to forward traffic to a newly created chain I get the following error:
>
> [root@home nftables]# nft add rule filter forward ip daddr 9.9.9.9 jump new
> <cmdline>:1:1-49: Error: Could not process rule in batch: Invalid argument
> add rule filter forward ip daddr 9.9.9.9 jump new
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Looks like an issue. I'm investigating into it.
BR,
--
Eric Leblond <eric@regit.org>
Blog: https://home.regit.org/
prev parent reply other threads:[~2013-11-15 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 16:53 nftables jump <chain> target invalid argument Alex Chapman
2013-11-15 13:06 ` Eric Leblond [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=1384520810.5425.2.camel@tiger2 \
--to=eric@regit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox