Revision tags: release/14.0.0 |
|
#
b3e76948 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
#
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
#
1de7b4b8 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0 |
|
#
3026fd06 |
| 06-Sep-2006 |
Brian Somers <brian@FreeBSD.org> |
If the peer REJects our MRU request and that request is for a value less than the current MTU, set our mtu to the value requested.
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0 |
|
#
eb1ecbb2 |
| 10-Jan-2005 |
Brian Somers <brian@FreeBSD.org> |
Integrate some OpenBSD alignment fixes. This hopefully also fixes PR 38058...
Obtained from: Brad <brad@comstyle.com>
|
#
125eb366 |
| 13-Dec-2004 |
Brian Somers <brian@FreeBSD.org> |
Implement an ``enable/disable echo'' option, defaults to off. This allows LCP ECHOs to be enabled independently of LQR reports.
Note: This introduces a change in the default behaviour (search for lq
Implement an ``enable/disable echo'' option, defaults to off. This allows LCP ECHOs to be enabled independently of LQR reports.
Note: This introduces a change in the default behaviour (search for lqr and echo in the man page). I'll update UPDATING to reflect this.
PR: 74821
show more ...
|
Revision tags: release/5.3.0_cvs, release/5.3.0 |
|
#
1814213e |
| 06-Sep-2004 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Fix the build on 64-bit platforms.
|
#
057f1760 |
| 05-Sep-2004 |
Brian Somers <brian@FreeBSD.org> |
Make ppp WARNS=5 clean
|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs |
|
#
6eafd353 |
| 27-Aug-2002 |
Brian Somers <brian@FreeBSD.org> |
Include the correct file (stdarg.h) and use va_list rather than _BSD_VA_LIST_
Suggested by: mike
|
Revision tags: release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs |
|
#
10be78d3 |
| 15-Jun-2002 |
Brian Somers <brian@FreeBSD.org> |
Remove whitespace at the end of lines.
|
#
de59e178 |
| 14-May-2002 |
Brian Somers <brian@FreeBSD.org> |
o Clean up some #includes o Bump version number to 3.0.4 o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal to the SES
o Clean up some #includes o Bump version number to 3.0.4 o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal to the SESSIONID from the environment in direct mode or the NGM_PPPOE_SESSIONID message in other modes. If no SESSIONID is found, default to the interface index in client mode or zero in server mode.
When the NAS-Port-Type is ISDN, set the NAS-Port to the minor number of the physical device (ie, the N in /dev/i4brbchN).
This makes it easier for the RADIUS server to identify the client WRT accounting data etc.
Prompted by: lsz8425 <lsz8425@mail.cd.hn.cn>
show more ...
|
#
69f6ed25 |
| 01-May-2002 |
Brian Somers <brian@FreeBSD.org> |
Allow the peer to modify the LQR interval
|
#
ff360cc9 |
| 17-Apr-2002 |
Brian Somers <brian@FreeBSD.org> |
Make the way FSM options are processed easier to read by using structures instead of u_char *.
The changes are cosmetic except:
RecvConfigAck() now displays the options that are being ACK'd Hug
Make the way FSM options are processed easier to read by using structures instead of u_char *.
The changes are cosmetic except:
RecvConfigAck() now displays the options that are being ACK'd Huge (bogus) options sent from the peer won't cause an infinite loop SendIdent and ReceiveIdent are displayed consistenlty with other FSM data LCP AUTHPROTO options that aren't understood are NAK'd, not REJ'd
show more ...
|
#
fb11a9c2 |
| 30-Mar-2002 |
Brian Somers <brian@FreeBSD.org> |
Merge the NETGRAPH branch into HEAD. tty devices now use netgraph's line discipline to do the async escaping, but no other benefits are available yet.
Change ``ifdef HAVE_DES'' to ``ifndef NODES''
Merge the NETGRAPH branch into HEAD. tty devices now use netgraph's line discipline to do the async escaping, but no other benefits are available yet.
Change ``ifdef HAVE_DES'' to ``ifndef NODES'' for consistency.
Make the Makefile a little more sane WRT RELEASE_CRUNCH.
show more ...
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
46df5aa7 |
| 03-Nov-2001 |
Brian Somers <brian@FreeBSD.org> |
Add a ``log'' command for logging specific information. Add an ``UPTIME'' variable to indicate the bundle uptime.
It's now possible to put something like this in ppp.linkdown for a server setup:
Add a ``log'' command for logging specific information. Add an ``UPTIME'' variable to indicate the bundle uptime.
It's now possible to put something like this in ppp.linkdown for a server setup:
MYADDR: log Session closing: User USER, address HISADDR, up UPTIME
Fixed some memory leakage with commands that expand words. Made some functions static. Fixed a diagnostic bug (iface add .... SIOCDIFADDR)
show more ...
|
#
542a7fe0 |
| 18-Oct-2001 |
Brian Somers <brian@FreeBSD.org> |
Fix AUTH callback negotiations.
MFC after: 1 week
|
#
2a772845 |
| 18-Oct-2001 |
Brian Somers <brian@FreeBSD.org> |
When the peer fails to specify an MRU and a 1500 byte MRU is not allowed either because of the transport or configuration, send a MRU NAK only once, then allow the negotiations to proceed.
rfc1661 s
When the peer fails to specify an MRU and a 1500 byte MRU is not allowed either because of the transport or configuration, send a MRU NAK only once, then allow the negotiations to proceed.
rfc1661 says that 1500 should always be allowed and rfc2516 says that 1492 is the maximum for PPPoE. This changes ppp so that it only weakly suggests 1492, then goes with the default (leaving the problem in the hands of the peer WRT how they set their MTU).
MFC after: 1 week
show more ...
|
#
ed1e8460 |
| 13-Sep-2001 |
Brian Somers <brian@FreeBSD.org> |
sigpause() -> sigsuspend() sigblock() -> sigprocmask()
|
#
30949fd4 |
| 14-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
o Add ipv6 support, abstracting most NCP addresses into opaque structures (well, they're treated as opaque).
It's now possible to manage IPv6 interface addresses and routing table entries and
o Add ipv6 support, abstracting most NCP addresses into opaque structures (well, they're treated as opaque).
It's now possible to manage IPv6 interface addresses and routing table entries and to filter IPV6 traffic whether encapsulated or not.
IPV6CP support is crude for now, and hasn't been tested against any other implementations.
RADIUS and IPv6 are independent of eachother for now.
ppp.linkup/ppp.linkdown aren't currently used by IPV6CP
o Understand all protocols(5) in filter rules rather than only a select few.
o Allow a mask specification for the ``delete'' command. It's now possible to specifically delete one of two conflicting routes.
o When creating and deleting proxy arp entries, do it for all IPv4 interface addresses rather than doing it just for the ``current'' peer address.
o When iface-alias isn't in effect, don't blow away manually (via ``iface add'') added interface addresses.
o When listening on a tcp server (diagnostic) socket, bind so that a tcp46 socket is created -- allowing both IPv4 and IPv6 connections.
o When displaying ICMP traffic, don't display the icmp type twice. When display traffic, display at least some information about unrecognised traffic.
o Bump version
Inspired after filtering work by: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
show more ...
|
#
5a082731 |
| 30-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
If the peer REJects our MRU REQ, stop REQing it -- *EVEN* if we're doing PPPoE and the default MRU is therefore too big.
When negotiating with win2k, we ask for MRU 1492 and the win2k box NAKs us sa
If the peer REJects our MRU REQ, stop REQing it -- *EVEN* if we're doing PPPoE and the default MRU is therefore too big.
When negotiating with win2k, we ask for MRU 1492 and the win2k box NAKs us saying ``MRU 1492''. This doesn't make sense to me. When we continue to request MRU 1492, the win2k box eventually REJs our MRU. This fix allows negotiations to continue at that point, bringing the link up and potentially allowing the win2k box to send us frames that are too large. AFAICT this is better than failing to bring the link up.... probably !
I have no idea how to do the equivalent of ``route get'' or ``ifconfig -a'' under win2k, so I can't tell what MTU it actually ends up using.
I believe the bug is in win2k (it's certainly mis-negotiating). I'll MFC given the release engineers permission as code freeze begins on August 1.
PR: 29277 MFC after: 3 days
show more ...
|
#
525b58c9 |
| 26-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Handle peer REQ/NAKs of >1500 byte MRUs when we have no preference.
MFC after: 3 days
|
#
17462195 |
| 17-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Ignore (with a warning message) mtu/mru configurations that are greater than the maximum physical values.
MFC after: 1 week
|
#
4bb6aac0 |
| 04-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Don't accept chap80lm by default - it doesn't work.
MFC after: 1 week
|
#
c8b9fb53 |
| 18-Jun-2001 |
Brian Somers <brian@FreeBSD.org> |
Handle hardware-imposed MTU/MRU limitations. PPPoE will no longer allow MRU/MTU negotiations to exceed 1492.
Add an optional ``max'' specifier to ``set m[rt]u'', ie.
set mtu max 1480
Bump the pp
Handle hardware-imposed MTU/MRU limitations. PPPoE will no longer allow MRU/MTU negotiations to exceed 1492.
Add an optional ``max'' specifier to ``set m[rt]u'', ie.
set mtu max 1480
Bump the ppp version number.
Sponsored by: Monzoon Networks AG and FreeBSD Services Limited
show more ...
|
#
65309e5c |
| 13-Jun-2001 |
Brian Somers <brian@FreeBSD.org> |
Convert IIJ copyrights to BSD copyrights.
Approved by: Toshiharu OHNO <tohno@sirius.ocn.ne.jp>
|