Date: Sun, 23 Jun 2024 19:23:12 +0000 From: bugzilla-noreply@freebsd.org To: pf@FreeBSD.org Subject: [Bug 279899] pf_unlink_state mutex unlock page fault panic Message-ID: <bug-279899-16861-eVGmw0Gm5Q@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279899-16861@https.bugs.freebsd.org/bugzilla/> References: <bug-279899-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=3D279899 --- Comment #2 from Daniel Ponte <amigan@gmail.com> --- (In reply to Kristof Provost from comment #1) Yes, eff27c3872300, sorry. This machine is primarily a NAT, IPv6 and VPN gateway for my home network, = but has some other roles (nginx reverse proxy, xmpp server, asterisk PBX). My ruleset is pretty complex and makes use of policy-based routing. The machine runs a vnet jail. I would rather not post the ruleset but would be happy to email it. I use pflogd, but no pfsync. --=20 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-279899-16861-eVGmw0Gm5Q>