From: Jake Owen <jake.owen@superloop.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nfqueue hashing on TCP/UDP port
Date: Wed, 16 Jun 2021 08:58:15 +1000 [thread overview]
Message-ID: <CAD353m=rR1zoFVSo+tF6YqCHEjuMW3UGcCZ2FLJWN5x1xAWcFg@mail.gmail.com> (raw)
In-Reply-To: <20210615130631.GC1425@breakpoint.cc>
Thank you Florian. I appreciate your thoughtful reply.
> To keep host-to-host comunication on the same queue, for ftp, sip and
> other highlevel protocols where a logical connection consists of
> multiple tcp/udp flows.
That does make a lot of sense.
> I will add arbitrary hash keying to nft, its currently
> only missing from the frontend.
>
> Will put you in CC when its done.
Thank you!
> With nft this will soon be possible:
>
> queue num jhash ip daddr . tcp sport . tcp dport mod 16
>
> ... which will queue to 0-15.
>
> I don't think we need code changes to the xtables backend.
That amount of flexibility looks wonderful.
prev parent reply other threads:[~2021-06-15 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 0:42 nfqueue hashing on TCP/UDP port Jake Owen
2021-06-15 13:06 ` Florian Westphal
2021-06-15 22:58 ` Jake Owen [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='CAD353m=rR1zoFVSo+tF6YqCHEjuMW3UGcCZ2FLJWN5x1xAWcFg@mail.gmail.com' \
--to=jake.owen@superloop.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).