On Tuesday 2020-06-16 16:48, Eugene Crosser wrote: > >2. Is it correct that "new generation" `nft` filtering infrastructure >does not support dynamically loadable extensions at all? (We need a >custom kernel module because we need access to the fields in the skb >that are not exposed to `nft`, and we need a custom extension to >configure the custom module.) Why not make a patch to publicly expose the skb's data via nft_meta? No more custom modules, no more userspace modifications, that would seem to be a win-win situation.
