[Bug 262971] pfctl: can't start pf or clear rules, DIOCADDRULENV:
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262971] pfctl: can't start pf or clear rules, DIOCADDRULENV:"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262971] pfctl: can't start pf or clear rules, DIOCADDRULENV, pfctl_clear_eth_rules: Device busy"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262971] pfctl: can't start pf or clear rules, DIOCADDRULENV, pfctl_clear_eth_rules: Device busy"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 01 Apr 2022 07:03:41 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262971
Bug ID: 262971
Summary: pfctl: can't start pf or clear rules, DIOCADDRULENV:
Product: Base System
Version: 13.1-STABLE
Hardware: arm64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: dch@freebsd.org
Created attachment 232853
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232853&action=edit
pf.conf
on reboot, pf doesn't start from rc.conf phase. I'm assuming this is some
malformed pf.conf on my side, but a line or rule # might help.
Enabling pfpfctl: DIOCADDRULENV: Invalid argument
/etc/rc: WARNING: Unable to load /etc/pf.conf.
pf.conf is attached:
# pfctl -vge -F all -f /etc/pf.conf
No ALTQ support in kernel
ALTQ related functions disabled
pfctl: pfctl_clear_eth_rules: Device busy
Seems to have broken between src commit aeb91e9 & 7d1ab86
a minimal test case is using pf.empty, literally an empty file:
# pfctl -vegf /etc/pf.empty
No ALTQ support in kernel
ALTQ related functions disabled
pfctl: pfctl_rules
# pfctl -F all
pfctl: pfctl_clear_eth_rules: Device busy
--
You are receiving this mail because:
You are the assignee for the bug.