[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200427234406.GA22616@salvia>
Date: Tue, 28 Apr 2020 01:44:06 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Lukas Wunner <lukas@...ner.de>
Cc: Laura Garcia <nevola@...il.com>,
Daniel Borkmann <daniel@...earbox.net>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Florian Westphal <fw@...len.de>,
Netfilter Development Mailing list
<netfilter-devel@...r.kernel.org>, coreteam@...filter.org,
netdev@...r.kernel.org, Martin Mares <mj@....cz>,
Dmitry Safonov <0x7f454c46@...il.com>,
Thomas Graf <tgraf@...g.ch>,
Alexei Starovoitov <ast@...nel.org>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH nf-next 3/3] netfilter: Introduce egress hook
Hi Lukas,
On Thu, Apr 23, 2020 at 06:05:42PM +0200, Lukas Wunner wrote:
[...]
> Daniel submitted a revert of this series but didn't cc me:
>
> https://lore.kernel.org/netdev/bbdee6355234e730ef686f9321bd072bcf4bb232.1584523237.git.daniel@iogearbox.net/
>
> In the ensuing discussion it turned out that the performance argument
> may be addressed by a rearrangement of sch_handle_egress() and
> nf_egress() invocations. I could look into amending the series
> accordingly and resubmitting, though I'm currently swamped with
> other work.
>
> The question is whether that's going to be sufficient because Daniel
> mentioned having an in-tree user as a prerequisite for accepting this
> feature, to which Pablo responded with NAT64/NAT46. I don't have
> intentions of implementing those, but maybe someone else has.
I'd love to work on integrating that feature, there are a few
implementations outthere that might be useful for this.
However, I'm terribly biased, I'm the Netfilter maintainer.
Even though, I really think this hook is going to be very useful for
the Linux community from day one.
Powered by blists - more mailing lists