Synopsis: [patch] ipfw(8) - don't get bitten by the fwd rule
State-Changed-From-To: open-closed
State-Changed-By: ae
State-Changed-When: Mon Jun 27 07:45:59 UTC 2011
State-Changed-Why:
The manual page already has a note about need of the custom kernel
configuration. When ipfw is used as module
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
Synopsis: [ipfw] [patch] ipfw_divert damages IPv6 packets
State-Changed-From-To: open-patched
State-Changed-By: ae
State-Changed-When: Mon Jun 27 12:53:05 UTC 2011
State-Changed-Why:
Patched in head/ with r223593.
http://www.freebsd.org/cgi/query-pr.cgi?pr=128260
I'm delighted to see that so much work is being done recently on ipfw,
i.e. patching.
But it also makes me wonder if there is anything new cooking for FreeBSD
9.0? Anybody knows?
Michael
___
freebsd-ipfw@freebsd.org mailing list
Synopsis: [patch] rc script for ipfw does not handle IPv6
Responsible-Changed-From-To: freebsd-ipfw-freebsd-rc
Responsible-Changed-By: ae
Responsible-Changed-When: Tue Jun 28 05:21:43 UTC 2011
Responsible-Changed-Why:
Reassign to freebsd-rc@.
This functionality is already present in head/ and
Synopsis: [ipfw] deadlock using multiple ipfw nat and multiple limit statements
State-Changed-From-To: open-feedback
State-Changed-By: ae
State-Changed-When: Tue Jun 28 05:29:45 UTC 2011
State-Changed-Why:
Can you still reproduce this on a supported release?
Or maybe you can test your rules on
Synopsis: [ipfw] ipfw stops to check packets for compliance with the rules,
letting everything Rules
State-Changed-From-To: open-feedback
State-Changed-By: ae
State-Changed-When: Tue Jun 28 05:36:11 UTC 2011
State-Changed-Why:
Can you still reproduce this?
It seems that you have misconfigured
