From: Florian Westphal <fw@strlen.de>
To: Antonio Ojea <aojea@google.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Eric Dumazet <edumazet@google.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] selftests: nft_queue: conntrack expiration requeue
Date: Tue, 21 Oct 2025 12:45:49 +0200 [thread overview]
Message-ID: <aPdkVOTuUElaFKZZ@strlen.de> (raw)
In-Reply-To: <CAAdXToQs8wPYyf=GEnNnmGXVTHQM0bkDfHGqVbLhber04AyM_w@mail.gmail.com>
Antonio Ojea <aojea@google.com> wrote:
> ct mark 0x66000000 ct state established,related accept
> queue flags bypass to 98
>
> So I just need to set the mark/label on the verdict and clear the mark
> or the label via netlink and it gets requeued.
>
> I can make it work with connmark very easily but labels seem a better
> fit because they allow me to set different values and avoid
> compatibility issues.
> However, I'm not able to make this work with labels, I do not know if
> it is a problem on my side, I'm not able to use the userspace
> conntrack tool too.
> I think I'm setting the label correctly but the output of conntrack -L
> or conntrack -L -o labels do not show anything.
> If I try to set the label manually it also fails with ENOSPC
>
> conntrack -U -d 10.244.2.2 --label-add net
> conntrack v1.4.8 (conntrack-tools): Operation failed: No space left on device
No space for the label extension.
Does it start to work for new flows when you add a rule like
'ct label foo'?
next prev parent reply other threads:[~2025-10-21 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 20:08 [PATCH] selftests: nft_queue: conntrack expiration requeue Antonio Ojea
2025-10-20 20:55 ` Florian Westphal
2025-10-20 21:23 ` Antonio Ojea
2025-10-20 22:08 ` Florian Westphal
2025-10-21 10:40 ` Antonio Ojea
2025-10-21 10:45 ` Florian Westphal [this message]
2025-10-21 12:05 ` Antonio Ojea
2025-10-21 12:18 ` Florian Westphal
2025-10-21 21:57 ` Antonio Ojea
2025-10-22 11:26 ` Florian Westphal
2025-10-22 14:15 ` Antonio Ojea
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aPdkVOTuUElaFKZZ@strlen.de \
--to=fw@strlen.de \
--cc=aojea@google.com \
--cc=edumazet@google.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).