PRs for tag 'ipf'
This is an experimental report containing PRs for tag 'ipf' as of 5-25-2012. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'ipf':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/03/12 | kern/165963 | net | [panic] [ipf] ipfilter/nat NULL pointer deference |
| o | 2008/05/18 | kern/123796 | net | [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not work |
| o | 2006/12/07 | kern/106438 | net | [ipf] ipfilter: keep state does not seem to allow replies in on spar64 (and maybe others) |
| o | 2006/08/12 | kern/101948 | net | [ipf] [panic] Kernel Panic Trap No 12 Page Fault - caused by IpFilter? |
| o | 2006/06/15 | kern/98978 | net | [ipf] [patch] ipfilter drops OOW packets under 6.1-Release |
| s | 2006/01/13 | kern/91777 | net | [ipf] [patch] wrong behaviour with skip rule inside an ipfilter group with a 'quick' head |
| o | 2005/10/16 | kern/87521 | net | [ipf] [panic] using ipfilter "auth" keyword leads to kernel fault [regression] |
| o | 2005/09/14 | kern/86103 | net | [ipf] Illegal NAT Traversal in IPFilter |
| o | 2005/02/25 | kern/78090 | net | [ipf] ipf filtering on bridged packets doesn't work if ipfw is loaded |
| s | 2005/02/07 | kern/77195 | net | [ipf] [patch] ipfilter ioctl SIOCGNATL does not match active sessions properly |
| o | 2004/08/24 | kern/70904 | net | [ipf] ipfilter ipnat problem with h323 proxy support |
| o | 2002/02/06 | kern/34665 | net | [ipf] [hang] ipfilter rcmd proxy "hangs". |
| o | 2001/05/20 | kern/27474 | net | [ipf] [ppp] Interactive use of user PPP and ipfilter can be insecure |
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.