[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aFhqUosjt2ptnlOZ@strlen.de>
Date: Sun, 22 Jun 2025 22:40:50 +0200
From: Florian Westphal <fw@...len.de>
To: Eric Woudstra <ericwouds@...il.com>
Cc: Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Nikolay Aleksandrov <razor@...ckwall.org>,
Ido Schimmel <idosch@...dia.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, netfilter-devel@...r.kernel.org,
bridge@...ts.linux.dev, netdev@...r.kernel.org
Subject: Re: [PATCH v12 nf-next 2/2] netfilter: nft_chain_filter: Add bridge
double vlan and pppoe
Eric Woudstra <ericwouds@...il.com> wrote:
> - return nft_do_chain(&pkt, priv);
> + ret = nft_do_chain(&pkt, priv);
> +
> + if (offset) {
> + __skb_push(skb, offset);
> + skb_reset_network_header(skb);
> + skb->protocol = outer_proto;
> + }
I don't think its a good idea to do this.
nft_do_chain() can mangle packet in arbitrary ways,
including making a duplicate, sending icmp/tcp resets in response
to packet. forwarding the packet to another interface, dropping
the packet, etc.
Wouldn't it be enough to set the skb network header if its not
set yet, without pull (and a need to push later)?
Powered by blists - more mailing lists