Summary: | panic: ipfw_check_frame: unknown retval - while trying to ipfw nat incoming packet without translation state (can be L2 firewall related) | ||
---|---|---|---|
Product: | Base System | Reporter: | bsd |
Component: | kern | Assignee: | freebsd-ipfw (Nobody) <ipfw> |
Status: | New --- | ||
Severity: | Affects Only Me | CC: | ae, bsd, melifaro, smithi |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
bsd
2017-02-02 07:52:03 UTC
Adding the "not layer2" to ipfw nat rule helps to avoid this problem (In reply to bsd from comment #1) You have set net.link.ether.ipfw=1b 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. |