Date: Wed, 03 Dec 2025 00:16:36 +0000 From: bugzilla-noreply@freebsd.org To: pf@FreeBSD.org Subject: [Bug 291357] pfctl: partial libxo support Message-ID: <bug-291357-16861-STmW7Ir3mP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291357-16861@https.bugs.freebsd.org/bugzilla/> References: <bug-291357-16861@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291357 --- Comment #2 from Leonid Evdokimov <leon+freebsd@darkk.net.ru> --- (In reply to Kristof Provost from comment #1) I totally agree. The only use-case I know for `--libxo -s rules` is to run `--libxo -s rules -vv` to get counters for the specific rule-number. It's an imaginary case to me, but it might sound like something realistic in some cases, e.g. it might be an input to some rule reordering machinery. I've not looked at the port in bug 284321 yet, but similar code might have a reason to consume those counters under some circumstances as well. And `-s labels` shows only rules having labels, so... :-) There might be some way to stitch libxo and `-s rules` together, but, absolutely, it'll be the last patch within the patchset. If any. The possible way to go I see is to make `--libxo -s rules` output somewhat similar to `--libxo -s labels` with the rule itself being serialized as a plain string. Otherwise I'd rather avoid `--libxo -s rules` altogether if it becomes to complex to review & merge. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291357-16861-STmW7Ir3mP>