PRs for manpage 'ipfw(8)'
This is an experimental report containing PRs for manpage 'ipfw(8)' as of Fri Mar 7 07:37:24 2014 UTC. See notes.
PRs for manpage 'ipfw(8)':
|o||2012/10/21||docs/172927||doc||ipfw(8): ipfw manual page doesn't show simpliest NAT case|
|o||2012/02/29||docs/165551||doc||ipfw(8): no info in "ipfw pipe show" about ipv6|
|o||2011/09/24||bin/160975||ipfw(8): ipfw's uid matching doesn't function with IPv6|
|o||2008/11/23||docs/129095||doc||ipfw(8): Can not check that packet originating/destined for local host|
|o||2008/11/20||docs/129024||keramida||[patch] ipfw(8) improvements|
|p||2006/10/30||bin/104921||melifaro||[patch] ipfw(8) sometimes treats ipv6 input as ipv4 (another variation on PR 91245)|
|o||2005/03/13||bin/78785||ipfw||[patch] ipfw(8) verbosity locks machine if /etc/rc.firewall is run remotely|
|o||2003/11/30||docs/59835||doc||ipfw(8) man page does not warn about accepted but meaningless rules|
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.