Hi Pablo,
I think you
have to do something similar to what Patrick did with nft_reject, by
adding a specific flavour of nft_meta for the bridge family.
In case of nft_meta, it would mean quite much code change,
since most of the keys are valid also for NFPROTO_BRIDGE.
Or maybe I miss something. (I don't know if it's proper to register a
second expr
in the same nft_meta.c, dedicated to bridge)
Wouldn't it be easier if I just check ctx->afi->family to be NFPROTO_BRIDGE
in nft_meta_init if the given key is one of the bridge related?
At evaluation, I can still check pkt->ops->pf as well.
Does the logic sound relevant?
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
