Date: Thu, 19 Jan 2023 05:10:00 +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-4NQ95kWqAZ@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 #30 from Kristof Provost <kp@freebsd.org> --- (In reply to jjasen from comment #29) We're looking at a deferred packet here, that's being allowed through, presumably after the pfsync peer ack'd the state. That should all just work, and I can't make it break in my test setup here. It looks like you have a setup where the packet is getting forwarded to an interface with a 9000 byte mtu, possibly after arriving on one with a 1500 = byte mtu. Does that sound familiar? I think it's getting confused about the IP length somehow. Can you do a 'p = *ip' and 'p/x *ip' in frame 10? That should print the IP header and may contain = more clues. --=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-4NQ95kWqAZ>