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

Site Navigation

PRs for manpage 'ppp(8)'

This is an experimental report containing PRs for manpage 'ppp(8)' as of Sun Apr 20 07:38:47 2014 UTC. See notes.


PRs for manpage 'ppp(8)':
SSubmittedTrackerResp.Description
o2010/09/02bin/150224netppp(8) does not reassign static IP after kill -KILL command
p2009/01/04bin/130159brian[patch] ppp(8) fails to correctly set routes
o2008/04/07bin/122519[patch] ppp(8): ppp provides deficient DNS info
o2008/03/04bin/121359maxim[patch] [security] ppp(8): fix local stack overflow in ppp
o2008/02/23bin/120994[patch] alignment violation in chap module of ppp(8) causes bus error on ARM
s2007/06/27bin/114081bz[patch] [ppp] ppp(8) should be able to set ethernet address for PPPoE
o2007/05/28bin/113074[patch] ppp(8): include <strings.h> for strcasecmp(3)
o2007/05/09bin/112557net[patch] ppp(8) lock file should not use symlink name
o2006/09/28bin/103762ppp(8): some tun interfaces with a mtu of 1500 while i should never exceed 1472 with ppp
o2004/04/30bin/66103ppp(8) macro HISADDR is not sticky in filters
o2003/05/28bin/52743ppp(8) /etc/ppp/ppp.linkup instability issues
o2003/05/20bin/52469ppp(8) Multiple devices using UDP don't work.
o2003/02/15bin/48309ppp(8) pppoe connections fail to establish if throughput disabled
s2002/10/15bin/44122ppp(8) tun0 gets a second ip adress after a disconnect
14 problems total.


Notes

GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.

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.