From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Laura García Liébana" <laura.garcia@zevenet.com>
Cc: netfilter@vger.kernel.org
Subject: Re: How to enable jhash for nftables v0.8
Date: Thu, 26 Oct 2017 11:34:09 +0200 [thread overview]
Message-ID: <20171026093409.GA6149@salvia> (raw)
In-Reply-To: <20171026092202.GA2589@salvia>
On Thu, Oct 26, 2017 at 11:22:02AM +0200, Pablo Neira Ayuso wrote:
> On Thu, Oct 26, 2017 at 11:09:26AM +0200, Laura García Liébana wrote:
> > > From: Zheng konia <konianet@gmail.com>
> > > Date: Thu, Oct 26, 2017 at 10:48 AM
> > > Subject: How to enable jhash for nftables v0.8
> > > To: Netfilter Users Mailing list <netfilter@vger.kernel.org>
> > >
> > >
> > > Hi,
> > >
> > > I'm have some error with configureing nftables-nat with loading
> > > balance when I trying `jhash`.
> > >
> > > # nft add rule nat prerouting mark set jhash ip saddr . tcp dport mod 2
> > > Error: Could not process rule: Invalid argument
> > > add rule nat prerouting mark set jhash ip saddr . tcp dport mod 2
> > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > Hi, the jhash expression it's correct but you should try with:
> >
> > # nft add rule ip nat prerouting ct mark set jhash ...
>
> Probably he doesn't want to set the mark... but match on it based on
> the jhash result.
I mean, the rule is valid. Although it may not make much sense? It's
just marking the first packet only.
Anyway, I suspect Zheng is running a kernel with no jhash support.
It would be good to document on the wiki since what kernel version
this is supported.
prev parent reply other threads:[~2017-10-26 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 8:48 How to enable jhash for nftables v0.8 Zheng konia
[not found] ` <CAF90-WiarOqxC4=OALo4gdsit4sohWmJR1rp+KXr+WecSvPiJg@mail.gmail.com>
2017-10-26 9:09 ` Laura García Liébana
2017-10-26 9:22 ` Pablo Neira Ayuso
2017-10-26 9:34 ` 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=20171026093409.GA6149@salvia \
--to=pablo@netfilter.org \
--cc=laura.garcia@zevenet.com \
--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.