Date: Sat, 04 Feb 2023 03:37:25 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 268246] crash and panic using pfsync on 13.1-RELEASE Message-ID: <bug-268246-7501-GubxLQnhYP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268246-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-268246-7501@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=3D268246 --- Comment #59 from jjasen@gmail.com --- (In reply to Nick Hilliard from comment #58) I've found outbound traffic from the secondary firewall will trigger the pfsyncintr issue, versus the pfsync_defer_tmo issue you posted.=20 You may want to try, depending on your environment, a puppet agent run on y= our backup firewall, a remote backup, scp'ing a crash dump to another machine, a 'pkg update', a freebsd-install fetch, and/or other remote connections forc= ing a pf state matching entry forcing a pfsync from the backup. Hope this helps! --=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-268246-7501-GubxLQnhYP>