[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b1ae75ac-82b5-aa24-c59a-3988d94d6a10@iogearbox.net>
Date: Tue, 8 Sep 2020 00:11:22 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Laura García Liébana <nevola@...il.com>
Cc: Lukas Wunner <lukas@...ner.de>,
John Fastabend <john.fastabend@...il.com>,
Pablo Neira Ayuso <pablo@...filter.org>,
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, Alexei Starovoitov <ast@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Thomas Graf <tgraf@...g.ch>, David Miller <davem@...emloft.net>
Subject: Re: [PATCH nf-next v3 3/3] netfilter: Introduce egress hook
On 9/5/20 1:18 PM, Laura García Liébana wrote:
> On Fri, Sep 4, 2020 at 11:14 PM Daniel Borkmann <daniel@...earbox.net> wrote:
[...]
> Something like this seems more trivial to me:
>
> table netdev mytable {
> chain mychain {
> type filter hook egress device "eth0" priority 100; policy drop;
> meta protocol != 0x419C accept
> }
> }
Sure, different frontends, so what?! You could also wrap that code into a
simple a.out or have nft style syntax jit to bpf ...
Powered by blists - more mailing lists