Synopsis: [ipfw] ipfw dynamic rules and fwd
State-Changed-From-To: open-patched
State-Changed-By: ae
State-Changed-When: Sat Jul 2 08:48:17 UTC 2011
State-Changed-Why:
Patched in head/.
http://www.freebsd.org/cgi/query-pr.cgi?pr=147720
___
F e l i z PRIMAVERA 2 0 3 1
drweschenfel...@gmail.com ( mailto:drweschenfel...@gmail.com )
rositapilott...@gmail.com ( mailto:rositapilott...@gmail.com )
CENTRO MEDICO REVITALIZARE®
Resistencia Chaco Argentina
Hola: queremos invitarte a la fiesta de PRIMAVERA del 2031 y a la de
AÑO NUEVO 2032.
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
Synopsis: [ipfw] deadlock using multiple ipfw nat and multiple limit statements
State-Changed-From-To: feedback-closed
State-Changed-By: ae
State-Changed-When: Sat Jul 2 19:42:05 UTC 2011
State-Changed-Why:
The submitter has reported that the problem is already fixed. Thanks!
Synopsis: [ipfw] Inconsistent via ipfw behavior
State-Changed-From-To: open-closed
State-Changed-By: ae
State-Changed-When: Sat Jul 2 20:44:50 UTC 2011
State-Changed-Why:
This is documented behaviour. ipfw(8) does not check interface names, because
they may be created dynamically.
via rule
