From 7f9a0204683f292f05577cd8b4dfc689cdd8e660 Mon Sep 17 00:00:00 2001 From: Florian Westphal Date: Wed, 30 Nov 2022 11:38:12 +0100 Subject: nft-bridge: work around recent "among" decode breakage ebtables-nft-save will fail with "unknown meta key" when decoding "among" emulation with ipv4 or ipv6 addresses included. This is because "meta protocol ip" is used as a dependency, but its never decoded anywhere. Skip this for now to restore the "ebtables/0006-flush_0" test case. Fixes: 25883ce88bfb ("nft: check for unknown meta keys") Signed-off-by: Florian Westphal Acked-by: Phil Sutter --- iptables/nft-bridge.c | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'iptables/nft-bridge.c') diff --git a/iptables/nft-bridge.c b/iptables/nft-bridge.c index 15dfc585..8d002c17 100644 --- a/iptables/nft-bridge.c +++ b/iptables/nft-bridge.c @@ -197,6 +197,11 @@ static void nft_bridge_parse_meta(struct nft_xt_ctx *ctx, uint8_t invflags = 0; char iifname[IFNAMSIZ] = {}, oifname[IFNAMSIZ] = {}; + switch (reg->meta_dreg.key) { + case NFT_META_PROTOCOL: + return; + } + if (parse_meta(ctx, e, reg->meta_dreg.key, iifname, NULL, oifname, NULL, &invflags) < 0) { ctx->errmsg = "unknown meta key"; return; -- cgit v1.2.3