Date: Tue, 28 Feb 2017 16:05:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ipfw@FreeBSD.org Subject: [Bug 216719] panic: ipfw_check_frame: unknown retval - while trying to ipfw nat incoming packet without translation state (can be L2 firewall related) Message-ID: <bug-216719-7515-GhIvvjoF20@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216719-7515@https.bugs.freebsd.org/bugzilla/> References: <bug-216719-7515@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=3D216719 smithi@nimnet.asn.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smithi@nimnet.asn.au --- Comment #2 from smithi@nimnet.asn.au --- (In reply to bsd from comment #1) You have set net.link.ether.ipfw=3D1b Are you using any rules for layer2 ? If not, set that to 0. If so, likely best to follow the example in ipfw(8) /PACKET FLOW to separate layer2 from layer 3 processing, otherwise every rule is tested on both layer2 and layer 3 passes, i.e. usually on each of 4 passes. Which is why adding 'not layer2' to the nat rule fixed it here, but other dragons may lie hidden in other rules checked at both layers. But of course, it shouldn't panic .. backtrace looks all layer2. --=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-216719-7515-GhIvvjoF20>