Date: Mon, 8 Sep 2008 02:22:21 GMT From: FreeBSD bugmaster <bugmaster@FreeBSD.org> To: freebsd-ipfw@FreeBSD.org Subject: Current problem reports assigned to freebsd-ipfw@FreeBSD.org Message-ID: <200809080222.m882MLfI006707@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o bin/127058 ipfw [patch] add "all" command line option to ipfw(8) table
o kern/126980 ipfw ipfw(8) hangs system
o bin/125370 ipfw [ipfw] [patch] increase a line buffer limit
o conf/123119 ipfw [patch] rc script for ipfw does not handle IPv6
o kern/122963 ipfw [ipfw] tcpdump does not show packets redirected by 'ip
s kern/121807 ipfw [request] TCP and UDP port_table in ipfw
o kern/121382 ipfw [dummynet]: 6.3-RELEASE-p1 page fault in dummynet (cor
o kern/121122 ipfw [ipfw] [patch] add support to ToS IP PRECEDENCE fields
o kern/118993 ipfw [ipfw] page fault - probably it's a locking problem
o kern/117234 ipfw [ipfw] [patch] ipfw send_pkt() and ipfw_tick() don't s
o kern/116009 ipfw [ipfw] [patch] Ignore errors when loading ruleset from
p kern/115755 ipfw [ipfw][patch] unify message and add a rule number wher
o bin/115172 ipfw [patch] ipfw(8) list show some rules with a wrong form
o docs/113803 ipfw [patch] ipfw(8) - don't get bitten by the fwd rule
p kern/113388 ipfw [ipfw][patch] Addition actions with rules within speci
o kern/112708 ipfw [ipfw] ipfw is seems to be broken to limit number of c
o kern/112561 ipfw [ipfw] ipfw fwd does not work with some TCP packets
o kern/107305 ipfw [ipfw] ipfw fwd doesn't seem to work
o kern/105330 ipfw [ipfw] [patch] ipfw (dummynet) does not allow to set q
o bin/104921 ipfw [patch] ipfw(8) sometimes treats ipv6 input as ipv4 (a
o kern/104682 ipfw [ipfw] [patch] Some minor language consistency fixes a
o kern/103454 ipfw [ipfw] [patch] [request] add a facility to modify DF b
o kern/103328 ipfw [ipfw] [request] sugestions about ipfw table
o kern/102471 ipfw [ipfw] [patch] add tos and dscp support
o kern/98831 ipfw [ipfw] ipfw has UDP hickups
o kern/97951 ipfw [ipfw] [patch] ipfw does not tie interface details to
o kern/97504 ipfw [ipfw] IPFW Rules bug
o kern/95084 ipfw [ipfw] [regression] [patch] IPFW2 ignores "recv/xmit/v
o kern/93300 ipfw [ipfw] ipfw pipe lost packets
o kern/91847 ipfw [ipfw] ipfw with vlanX as the device
o kern/88659 ipfw [modules] ipfw and ip6fw do not work properly as modul
o kern/87032 ipfw [ipfw] [patch] ipfw ioctl interface implementation
o kern/86957 ipfw [ipfw] [patch] ipfw mac logging
o kern/82724 ipfw [ipfw] [patch] [request] Add setnexthop and defaultrou
s kern/80642 ipfw [ipfw] [patch] ipfw small patch - new RULE OPTION
o bin/78785 ipfw [patch] ipfw(8) verbosity locks machine if /etc/rc.fir
o kern/74104 ipfw [ipfw] ipfw2/1 conflict not detected or reported, manp
o kern/73910 ipfw [ipfw] serious bug on forwarding of packets after NAT
o kern/72987 ipfw [ipfw] ipfw/dummynet pipe/queue 'queue [BYTES]KBytes (
o kern/71366 ipfw [ipfw] "ipfw fwd" sometimes rewrites destination mac a
o kern/69963 ipfw [ipfw] install_state warning about already existing en
o kern/60719 ipfw [ipfw] Headerless fragments generate cryptic error mes
o kern/55984 ipfw [ipfw] [patch] time based firewalling support for ipfw
o kern/51274 ipfw [ipfw] [patch] ipfw2 create dynamic rules with parent
o kern/48172 ipfw [ipfw] [patch] ipfw does not log size and flags
o kern/46159 ipfw [ipfw] [patch] [request] ipfw dynamic rules lifetime f
a kern/26534 ipfw [ipfw] Add an option to ipfw to log gid/uid of who cau
47 problems total.
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809080222.m882MLfI006707>