Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'ipfw(8)'

This is an experimental report containing PRs for manpage 'ipfw(8)' as of Thu Apr 24 07:37:30 2014 UTC. See notes.


PRs for manpage 'ipfw(8)':
SSubmittedTrackerResp.Description
o2014/03/24bin/187904ipfw[ipfw] ipfw(8) does not properly recognize the network in shorthand [regression]
o2012/10/21docs/172927docipfw(8): ipfw manual page doesn't show simpliest NAT case
o2012/02/29docs/165551docipfw(8): no info in "ipfw pipe show" about ipv6
o2011/09/24bin/160975ipfw(8): ipfw's uid matching doesn't function with IPv6
o2008/11/23docs/129095docipfw(8): Can not check that packet originating/destined for local host
o2008/11/20docs/129024keramida[patch] ipfw(8) improvements
p2006/10/30bin/104921melifaro[patch] ipfw(8) sometimes treats ipv6 input as ipv4 (another variation on PR 91245)
o2005/03/13bin/78785ipfw[patch] ipfw(8) verbosity locks machine if /etc/rc.firewall is run remotely
o2003/11/30docs/59835docipfw(8) man page does not warn about accepted but meaningless rules
9 problems total.


Notes

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.