From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Sven Auhagen <Sven.Auhagen@voleatech.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] nf_flowtable: nft_flow_route use more data for reverse route
Date: Mon, 9 May 2022 08:16:03 +0200 [thread overview]
Message-ID: <Ynixo9mxKqMbq3Ie@salvia> (raw)
In-Reply-To: <20220427071515.qfgqbs6uzoowwnkg@SvensMacbookPro.hq.voleatech.com>
On Wed, Apr 27, 2022 at 09:15:15AM +0200, Sven Auhagen wrote:
> When creating a flow table entry, the reverse route is looked
> up based on the current packet.
> There can be scenarios where the user creates a custom ip rule
> to route the traffic differently.
> In order to support those scenarios, the lookup needs to add
> more information based on the current packet.
> The patch adds multiple new information to the route lookup.
Applied, thanks
next prev parent reply other threads:[~2022-05-09 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:15 [PATCH] nf_flowtable: nft_flow_route use more data for reverse route Sven Auhagen
2022-05-09 6:16 ` Pablo Neira Ayuso [this message]
2022-05-10 9:28 ` [nf_flowtable] 2cd764935d: kernel-selftests.netfilter.nft_flowtable.sh.ipsec_tunnel_mode_for_ns1/ns2.fail kernel test robot
2022-05-10 9:58 ` Pablo Neira Ayuso
2022-05-12 6:03 ` Oliver Sang
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=Ynixo9mxKqMbq3Ie@salvia \
--to=pablo@netfilter.org \
--cc=Sven.Auhagen@voleatech.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