From: "Laura García Liébana" <nevola@gmail.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
coreteam@netfilter.org, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Eric Dumazet <edumazet@google.com>, Thomas Graf <tgraf@suug.ch>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH nf-next v3 0/3] Netfilter egress hook
Date: Thu, 27 Aug 2020 12:36:55 +0200 [thread overview]
Message-ID: <CAF90-Wi4W1U4FSYqyBTqe7sANbdO6=zgr-u+YY+X-gvNmOgc6A@mail.gmail.com> (raw)
In-Reply-To: <cover.1598517739.git.lukas@wunner.de>
Hi Lukas, thank you for your patches.
On Thu, Aug 27, 2020 at 10:55 AM Lukas Wunner <lukas@wunner.de> wrote:
>
> Introduce a netfilter egress hook to allow filtering outbound AF_PACKETs
> such as DHCP and to prepare for in-kernel NAT64/NAT46.
>
Actually, we've found 2 additional use cases in container-based nodes
that use the egress hook:
1. intra-node DSR load balancing connectivity
2. container-based outbound security policies
We've been using your previous patch in an experimental project and
it's working fine.
Great job!
next prev parent reply other threads:[~2020-08-27 10:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 8:55 [PATCH nf-next v3 0/3] Netfilter egress hook Lukas Wunner
2020-08-27 8:55 ` [PATCH nf-next v3 1/3] netfilter: Rename ingress hook include file Lukas Wunner
2020-08-27 8:55 ` [PATCH nf-next v3 2/3] netfilter: Generalize ingress hook Lukas Wunner
2020-08-27 8:55 ` [PATCH nf-next v3 3/3] netfilter: Introduce egress hook Lukas Wunner
2020-08-28 18:52 ` John Fastabend
2020-09-03 5:00 ` John Fastabend
2020-09-04 8:54 ` Laura García Liébana
2020-09-04 15:46 ` John Fastabend
2020-09-05 11:13 ` Laura García Liébana
2020-09-04 16:21 ` Lukas Wunner
2020-09-04 21:14 ` Daniel Borkmann
2020-09-05 5:24 ` Lukas Wunner
2020-09-08 12:55 ` Daniel Borkmann
2020-09-11 7:42 ` Laura García Liébana
2020-09-11 16:27 ` Daniel Borkmann
2020-09-14 11:29 ` Laura García Liébana
2020-09-14 22:02 ` Daniel Borkmann
2020-09-17 10:28 ` Laura García Liébana
2020-09-18 20:31 ` Daniel Borkmann
2020-09-19 15:52 ` Pablo Neira Ayuso
2020-09-21 7:07 ` Laura García Liébana
2020-10-11 8:26 ` Lukas Wunner
2020-11-21 18:59 ` Pablo Neira Ayuso
2020-11-22 3:24 ` Alexei Starovoitov
2020-11-22 11:01 ` Pablo Neira Ayuso
2020-11-24 3:34 ` Alexei Starovoitov
2020-11-24 7:31 ` Lukas Wunner
2020-11-24 22:55 ` Alexei Starovoitov
2020-10-11 7:59 ` Lukas Wunner
2020-09-05 11:18 ` Laura García Liébana
2020-09-07 22:11 ` Daniel Borkmann
2020-09-08 6:19 ` Laura García Liébana
2020-09-08 11:46 ` Arturo Borrero Gonzalez
2020-09-08 13:27 ` Daniel Borkmann
2020-09-08 18:58 ` John Fastabend
2020-09-19 15:54 ` Pablo Neira Ayuso
2020-09-28 12:20 ` Lukas Wunner
2020-08-27 10:36 ` Laura García Liébana [this message]
2020-08-28 7:14 ` [PATCH nf-next v3 0/3] Netfilter " Daniel Borkmann
2020-08-28 9:14 ` Eric Dumazet
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='CAF90-Wi4W1U4FSYqyBTqe7sANbdO6=zgr-u+YY+X-gvNmOgc6A@mail.gmail.com' \
--to=nevola@gmail.com \
--cc=ast@kernel.org \
--cc=coreteam@netfilter.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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).