Re: [PATCH] selftests: nft_queue: conntrack expiration requeue

[Antonio Ojea <aojea@google.com>]

> Looks like one needs to set a label somewhere, no need for it to match.
>
> chain never { ct label set foo }
>
> makes this work for me.
> We could change this so that *checking* a label also turns on the
> extension infra.
>
> Back then i did not want to allocate the extra space for
> the extensions and i did not want to add to a new sysctl either.
>
> So I went with 'no rules that adds one, no need for ct label
> extension space allocation'.

But that does not consider the people that just use netlink to set the
labels ... from a 1k altitude , can you do a check on the first
update/create/delete label to initialize the extension?


Another question related, is it required for the label value to be
always 16 bytes?
I do not know if is the golang libraries I'm using but it seems it
does not work with other lengths