PRs for tag 'ipfw'
This is an experimental report containing PRs for tag 'ipfw' 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 'ipfw':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/05/12 | conf/167822 | ipfw | [ipfw] [patch] start script doesn't load firewall_type if set in rc.conf.d/ipfw |
| o | 2012/03/26 | kern/166406 | ipfw | [ipfw] ipfw does not set ALTQ identifier for ipv6 traffic |
| o | 2012/02/15 | kern/165190 | ipfw | [ipfw] [lo] [patch] loopback interface is not marking ipv6 packets |
| p | 2012/02/01 | kern/164690 | melifaro | [ipfw] Request for ipv6 support in ipfw tables |
| f | 2012/01/06 | kern/163873 | ipfw | [ipfw] ipfw fwd does not work with 'via interface' in rule body |
| o | 2011/06/20 | kern/158066 | ipfw | [ipfw] ipfw + netgraph + multicast = multicast packets transmitted over wrong interface |
| o | 2011/06/12 | kern/157796 | ipfw | [ipfw] IPFW in-kernel NAT nat loopback / Default Router Changes Unexpectedly |
| o | 2011/06/07 | kern/157689 | ipfw | [ipfw] ipfw nat config does not accept nonexistent interfaces |
| o | 2011/05/02 | kern/156770 | ipfw | [ipfw] [dummynet] [patch]: performance improvement and several extensions |
| o | 2011/04/08 | kern/156279 | net | [if_bridge][divert][ipfw] unable to correctly re-inject packets into an unnumbered, bridged interface using divert sockets |
| f | 2011/03/25 | kern/155927 | ipfw | [ipfw] ipfw stops to check packets for compliance with the rules, letting everything Rules |
| o | 2010/12/17 | bin/153252 | ipfw | [ipfw][patch] ipfw lockdown system in subsequent call of "/etc/rc.d/ipfw start" |
| o | 2010/12/15 | kern/153161 | ipfw | [ipfw] does not support specifying rules with ICMP codes |
| o | 2010/11/10 | kern/152113 | ipfw | [ipfw] page fault on 8.1-RELEASE caused by certain amount of traffic through router |
| o | 2010/07/25 | kern/148928 | hrs | [ipfw] Problem with loading of ipfw NAT rules during system startup |
| o | 2010/07/21 | kern/148827 | ipfw | [ipfw] divert broken with in-kernel ipfw |
| o | 2010/07/16 | kern/148689 | ipfw | [ipfw] antispoof wrongly triggers on link local IPv6 addresses |
| o | 2010/07/07 | kern/148430 | ipfw | [ipfw] IPFW schedule delete broken. |
| o | 2010/06/25 | conf/148137 | hrs | [ipfw] call order of natd and ipfw startup scripts |
| o | 2010/06/23 | kern/148091 | ipfw | [ipfw] ipfw ipv6 handling broken. |
| f | 2010/02/26 | kern/144315 | net | [ipfw] [panic] freebsd 8-stable reboot after add ipfw rules with netgraph ng_car |
| o | 2010/02/15 | kern/143973 | ipfw | [ipfw] [panic] ipfw forward option causes kernel reboot |
| o | 2010/02/07 | kern/143621 | ipfw | [ipfw] [dummynet] [patch] dummynet and vnet use results in panic |
| o | 2009/08/02 | kern/137346 | ipfw | [ipfw] ipfw nat redirect_proto is broken |
| o | 2009/07/29 | kern/137232 | ipfw | [ipfw] parser troubles |
| o | 2009/06/11 | kern/135476 | ipfw | [ipfw] IPFW table breaks after adding a large number of values |
| o | 2009/03/18 | kern/132774 | rwatson | [ipfw] IPFW with uid/gid/jail rules may lead to lockup |
| o | 2009/01/02 | kern/130109 | net | [ipfw] Can not set fib for packets originated from local host |
| o | 2008/11/21 | kern/129036 | ipfw | [ipfw] 'ipfw fwd' does not change outgoing interface name |
| p | 2008/10/21 | kern/128260 | ipfw | [ipfw] [patch] ipfw_divert damages IPv6 packets |
| o | 2008/09/09 | kern/127230 | ipfw | [ipfw] [patch] Feature request to add UID and/or GID logging data to ipfw logging with uid rules. |
| a | 2008/05/03 | kern/123358 | [ipfw] ipfw add 1000 allow IP from any to any doesn't work | |
| f | 2008/04/21 | kern/122963 | ipfw | [ipfw] tcpdump does not show packets redirected by 'ipfw fwd' on proper interface |
| o | 2008/02/26 | kern/121122 | ipfw | [ipfw] [patch] add support to ToS IP PRECEDENCE fields |
| o | 2007/09/02 | kern/116009 | ipfw | [ipfw] [patch] Ignore errors when loading ruleset from file + rule replacement command |
| o | 2006/10/22 | kern/104682 | ipfw | [ipfw] [patch] Some minor language consistency fixes and whitespace nits |
| o | 2006/09/21 | kern/103454 | ipfw | [ipfw] [patch] [request] add a facility to modify DF bit of the IP packet |
| o | 2006/09/17 | kern/103328 | ipfw | [ipfw] [request] sugestions about ipfw table |
| o | 2006/08/24 | kern/102471 | ipfw | [ipfw] [patch] add tos and dscp support |
| o | 2006/05/26 | kern/97951 | ipfw | [ipfw] [patch] ipfw does not tie interface details to state |
| o | 2006/03/29 | kern/95084 | ipfw | [ipfw] [regression] [patch] IPFW2 ignores "recv/xmit/via any" (IPFW1->2 regression) |
| o | 2005/10/05 | kern/86957 | ipfw | [ipfw] [patch] ipfw mac logging |
| o | 2005/07/06 | bin/83046 | ipfw | [ipfw] ipfw2 error: "setup" is allowed for icmp, but shouldn't be |
| o | 2005/06/28 | kern/82724 | ipfw | [ipfw] [patch] [request] Add setnexthop and defaultroute features to ipfw2 |
| o | 2004/04/25 | bin/65961 | ipfw | [ipfw] ipfw2 memory corruption inside add() |
| o | 2004/01/28 | kern/62042 | luigi | [ipfw] ipfw can't no more reject icmp (icmptypes 8) |
| o | 2003/12/30 | kern/60719 | ipfw | [ipfw] Headerless fragments generate cryptic error message |
| o | 2003/08/27 | kern/56031 | luigi | [ipfw] ipfw hangs on every invocation |
| s | 2003/08/26 | kern/55984 | ipfw | [ipfw] [patch] time based firewalling support for ipfw2 |
| s | 2003/04/24 | kern/51341 | remko | [ipfw] [patch] ipfw rule 'deny icmp from any to any icmptype 5' matches fragmented icmp packets |
| o | 2003/02/11 | kern/48172 | ipfw | [ipfw] [patch] ipfw does not log size and flags |
| o | 2002/12/10 | kern/46159 | ipfw | [ipfw] [patch] [request] ipfw dynamic rules lifetime feature |
| a | 2001/04/13 | kern/26534 | ipfw | [ipfw] Add an option to ipfw to log gid/uid of who caused the rule |
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.