https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280516
Bug ID: 280516
Summary: blacklistd: Silence a bogus warning about the
blacklistd anchor not being found
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: b...@freebsd.org
Reporter: jldu...@gmail.com
Created attachment 252376
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252376&action=edit
Silence a bogus warning when starting up
Silence a bogus warning when starting up:
Anchor 'blacklistd' not found.
The anchor is indeed there, and working correctly.
To my untrained eye, it looks like a bug in pfctl.c (see the attached diff with
the sample pf.conf):
# pfctl -a blacklistd -sa | grep XXX
pfctl: XXX DIOCGETETHRULES: No such file or directory
pfctl: XXX DIOCGETRULES: Invalid argument
pfctl: XXX DIOCGETRULES: Invalid argument
pfctl: XXX DIOCGETRULES: Invalid argument
The warning from blacklistd stems from:
# pfctl -a blacklistd -sA
XXX Anchor 'blacklistd' not found.
Evidently the anchor is there, it's just "empty", and the warning seems
misleading.
# /usr/libexec/blacklistd-helper add blacklistd tcp 198.51.100.0 24 22 1
# pfctl -a blacklistd -sA
blacklistd/22
It might be related to bug #262590.
--
You are receiving this mail because:
You are the assignee for the bug.
