PRs for tag 'pf'
This is an experimental report containing PRs for tag 'pf' as of 5-30-2014. 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 'pf':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/04/27 | kern/189060 | pf | [pf] pf + altq doesn't work on octe (Edgerouter Lite) [regression] |
| o | 2014/04/12 | kern/188511 | pf | [pf] [patch] divert-reply implementation for pf |
| o | 2014/04/02 | kern/188188 | pf | [pf] [panic] pfsync0 mtu 9000 results in 10-STABLE reboot |
| o | 2014/03/29 | kern/188063 | pf | [pf] [hang] deadlock between syncache(4) and pf(4) |
| f | 2014/03/14 | kern/187566 | pf | [pf] incoming ng_l2tp/ipsec packet bypass PF firewall |
| o | 2014/01/10 | kern/185633 | [pf] scrubbing bug in transparent mode bug with bigger than MTU UDP packet | |
| f | 2013/12/04 | kern/184485 | glebius | [pf] pfioctl causing kernel panics in 10-BETA{3,4} |
| o | 2013/10/22 | kern/183198 | pf | [pf] pf tables not loaded if only used inside anchor |
| o | 2013/09/26 | kern/182401 | pf | [pf] pf state for some IPs reaches 4294967295 suspicously |
| o | 2013/09/24 | kern/182350 | pf | [pf] core dump with packet filter -- pf_overlad_task |
| o | 2013/06/07 | kern/179392 | pf | [pf] [ip6] Incorrect TCP checksums in rdr return packets |
| a | 2013/06/03 | kern/179264 | net | [vimage] [pf] Core dump with Packet filter and VIMAGE options compile in a kernel |
| o | 2013/04/12 | kern/177810 | pf | [pf] traffic dropped by accepting rules is not counted |
| o | 2013/04/12 | kern/177808 | pf | [pf] [patch] route-to rule forwarding traffic inspite of state limit |
| o | 2013/03/26 | kern/177402 | net | [igb] [pf] problem with ethernet driver igb + pf / altq [regression] |
| o | 2013/02/19 | kern/176268 | pf | [pf] [patch] synproxy not working with route-to |
| o | 2013/01/13 | kern/175267 | net | [pf] [tap] pf + tap keep state problem |
| o | 2012/10/12 | kern/172648 | pf | [pf] [ip6]: 'scrub reassemble tcp' breaks IPv6 packet checksum on SYN ACK |
| o | 2012/09/18 | kern/171733 | pf | [pf] PF problem with modulate state in [regression] |
| o | 2012/07/03 | kern/169630 | pf | [pf] [patch] pf fragment reassembly of padded (undersized) fragments |
| o | 2012/07/03 | kern/169620 | pf | [ng] [pf] ng_l2tp incoming packet bypass pf firewall |
| o | 2012/06/11 | kern/168952 | pf | [pf] direction scrub rules don't work |
| o | 2012/05/21 | kern/168190 | pf | [pf] panic when using pf and route-to (maybe: bad fragment handling?) |
| a | 2012/03/29 | kern/166501 | andre | [pf] FreeBSD 9.0 generates incorrect SEC/ACK numbers under load |
| o | 2012/03/23 | kern/166336 | pf | [pf] kern.securelevel 3 +pf reload |
| o | 2012/02/20 | kern/165315 | pf | [pf] States never cleared in PF with DEVICE_POLLING |
| o | 2012/02/17 | kern/165252 | virtualization | [vimage] [pf] [panic] kernel panics with VIMAGE and PF on FreeBSD 9.0 rel |
| o | 2012/01/23 | kern/164402 | pf | [pf] pf crashes with a particular set of rules when first matching packet arrives |
| o | 2012/01/18 | kern/164271 | pf | [pf] not working pf nat on FreeBSD 9.0 [regression] |
| o | 2011/12/12 | kern/163208 | pf | [pf] PF state key linking mismatch |
| o | 2011/09/28 | kern/161094 | virtualization | [vimage] [pf] [panic] kernel panic with pf + VIMAGE when stopping a jail |
| o | 2011/09/07 | kern/160541 | virtualization | [vimage][pf][patch] panic: userret: Returning on td 0xxxxxxxxx (pid xxxx, pftop) with vnet 0xxxxxxxxx set in pfioctl |
| o | 2011/09/06 | kern/160496 | virtualization | [vimage] [pf] [patch] kernel panic with pf + VIMAGE |
| o | 2011/09/01 | kern/160370 | pf | [pf] Incorrect pfctl check of pf.conf |
| o | 2011/03/20 | kern/155736 | pf | [pf] [altq] borrow from parent queue does not work with cbq |
| o | 2010/12/20 | kern/153307 | pf | [pf] Bug with PF firewall |
| o | 2010/07/01 | kern/148290 | pf | [pf] "sticky-address" option of Packet Filter (PF) blocks connection |
| o | 2010/06/30 | kern/148260 | pf | [pf] [patch] pf rdr incompatible with dummynet |
| o | 2010/06/26 | kern/148155 | virtualization | [vimage] [pf] Kernel panic with PF + VIMAGE kernel option |
| o | 2010/06/11 | kern/147789 | pf | [pf] Firewall PF no longer drops connections by sending TCP RST packets |
| o | 2010/05/22 | kern/146832 | gnn | [pf] "(self)" not always matching all local IPv6 addresses |
| o | 2010/05/18 | kern/146719 | net | [pf] [panic] PF or dumynet kernel panic |
| o | 2010/02/26 | kern/144311 | gnn | [pf] [icmp] massive ICMP storm on lo0 occurs when using pf(4) 'reply-to' |
| s | 2010/02/11 | kern/143808 | virtualization | [pf] pf does not work inside jail |
| o | 2010/02/04 | kern/143543 | pf | [pf] [panic] PF route-to causes kernel panic |
| o | 2010/01/19 | conf/142961 | pf | [pf] No way to adjust pidfile in pflogd |
| o | 2009/12/22 | kern/141905 | pf | [pf] [panic] pf kernel panic on 7.2-RELEASE with empty pf.conf |
| o | 2009/11/19 | kern/140697 | pf | [pf] pf behaviour changes - must be documented |
| o | 2009/08/20 | kern/137982 | pf | [pf] when pf can hit state limits, random IP failures and no debugging info is provided |
| o | 2009/07/15 | kern/136781 | pf | [pf] Packets appear to drop with pf scrub and if_bridge |
| o | 2009/07/09 | kern/136618 | net | [pf][stf] panic on cloning interface without unit number, e.g. `stf' |
| o | 2009/06/23 | kern/135948 | pf | [pf] [gre] pf not natting gre protocol |
| o | 2009/05/27 | kern/134996 | pf | [pf] Anchor tables not included when pfctl(8) is run with -o |
| o | 2009/04/14 | kern/133732 | pf | [pf] max-src-conn issue |
| o | 2009/01/11 | conf/130381 | pf | [rc.d] [pf] [ip6] ipv6 not fully configured when pf startup script is run |
| o | 2008/10/07 | kern/127920 | pf | [pf] ipv6 and synproxy don't play well together |
| o | 2008/10/03 | conf/127814 | pf | [pf] The flush in pf_reload in /etc/rc.d/pf does not work as intended |
| o | 2008/09/05 | kern/127121 | pf | [pf] [patch] pf incorrect log priority |
| o | 2008/09/02 | kern/127042 | pf | [pf] [patch] pf recursion panic if interface group is the same as the new interface name |
| o | 2008/07/10 | kern/125467 | pf | [pf] pf keep state bug while handling sessions between vlan trunk |
| s | 2008/06/24 | kern/124933 | pf | [pf] [ip6] pf does not support (drops) IPv6 fragmented packets |
| o | 2008/04/14 | kern/122773 | pf | [pf] pf doesn't log uid or pid when configured to |
| o | 2008/03/23 | kern/122014 | pf | [pf] [panic] FreeBSD 6.2 panic in pf |
| o | 2008/02/05 | kern/120281 | pf | [pf] [request] lost returning packets to PF for a rdr rule |
| o | 2008/01/27 | kern/120057 | pf | [pf] [patch] Allow proper settings of ALTQ_HFSC. The check i wrong since even with the values forbidden from this check you get a concave curve. |
| o | 2007/11/30 | bin/118355 | pf | [pf] [patch] pfctl(8) help message options order false -t must before -T |
| o | 2007/07/13 | kern/114567 | pf | [pf] [lor] pf_ioctl.c + if.c |
| o | 2006/02/25 | kern/93825 | pf | [pf] pf reply-to doesn't work |
| o | 2006/02/18 | sparc64/93530 | pf | [pf] Incorrect checksums when using pf's route-to on sparc64 |
| o | 2006/02/07 | kern/92949 | pf | [pf] PF + ALTQ problems with latency |
| o | 2005/10/07 | kern/87074 | pf | [pf] pf does not log dropped packets when max-* stateful tracking options watermark are reached |
| a | 2005/09/30 | kern/86752 | pf | [pf] pf does not use default timeouts when reloading config file |
| o | 2005/06/15 | kern/82271 | pf | [pf] cbq scheduler cause bad latency |
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.