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

Site Navigation

PRs for tag 'stf'

This is an experimental report containing PRs for tag 'stf' 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 Thanks.

PRs for tag 'stf':
o2011/01/22kern/154214net[stf] [panic] Panic when creating stf interface
o2010/06/20conf/148017hrs[stf] [patch] rc script for stf does not honour create_flags
s2010/02/08kern/143673net[stf] [request] there should be a way to support multiple 6to4 addresses
o2009/07/09kern/136618net[pf][stf] panic on cloning interface without unit number, e.g. `stf'
o2008/05/21kern/123858net[stf] [patch] stf not usable behind a NAT
5 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.