Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
a12856cf |
| 22-Nov-2001 |
Brian Somers <brian@FreeBSD.org> |
Expand the first argument of the ``log'' command if it's a variable.
|
#
39d2e655 |
| 04-Nov-2001 |
Brian Somers <brian@FreeBSD.org> |
Remove unused variables
|
#
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 ...
|
#
dad51e5c |
| 23-Oct-2001 |
Brian Somers <brian@FreeBSD.org> |
Don't avoid setting a 0 second timer in datalink_StartDialTimer() by not setting any timer. Instead, set a 1 millisecond timer.
This ensures that ppp will come out of it's select() call after losin
Don't avoid setting a 0 second timer in datalink_StartDialTimer() by not setting any timer. Instead, set a 1 millisecond timer.
This ensures that ppp will come out of it's select() call after losing carrier in -ddial mode with a reconnect period of 0 and going to ST_OPENING, rather than waiting indefinitely for some other event to wake ppp up.
Bump the ppp version number to indicate the event.
MFC after: 3 days
show more ...
|
#
2313781d |
| 20-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Handle snprintf() returning < 0 (not just -1)
MFC after: 2 weeks
|
#
1433aa5d |
| 19-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Better handling for the return of snprintf().
|
#
1136c6ac |
| 18-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Back out the previous fix to deal with kernels that don't support IPv6, and implement a far more subtle and correct fix.
The reason behind the infinite loop was that ppp was trying to make up initia
Back out the previous fix to deal with kernels that don't support IPv6, and implement a far more subtle and correct fix.
The reason behind the infinite loop was that ppp was trying to make up initial IPv6 numbers and wasn't giving up when it failed unexpectedly to assign the addresses it just fabricated to it's interface (thinking that the reason was because another interface was using the same address). It now attempts this up to 100 times before just failing and trying to muddle along (in reality, this should never happen more than a couple of times unless our random number generator doesn't work).
Also, when IPv6 is not available, don't even try to assign the IPv6 interface address in the first place...
show more ...
|
#
c5109a32 |
| 18-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Run correctly on a machine built without AF_INET6 support
|
#
6c764d89 |
| 18-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Build properly with -DNOIPV6
|
#
e1a94c3d |
| 16-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Remove an unused variable
|
#
971abb29 |
| 15-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Probe for the availability of AF_INET6 at startup. If it's not available, default ipv6cp to disabled and refuse to let the user enable it.
|
#
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 ...
|
#
686e8c8b |
| 02-Aug-2001 |
Brian Somers <brian@FreeBSD.org> |
Add a ``nat punch_fw'' command for punching FTP and IRC DCC holes through the firewall.
|
#
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
|
#
b5b15b9e |
| 09-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Fix the type of the last arg to execl()
Obtained from: OpenBSD
|
#
88298994 |
| 09-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Add a ``nat proto'' command -- similar to natd(8)'s -redirect_proto switch.
MFC after: 3 weeks
|
#
80a18377 |
| 07-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Spell stateful properly
Inconsistently done by: brian Spotted by: ru
|
#
f2e587a3 |
| 04-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Silence some gcc warnings
|
#
7aab014b |
| 03-Jul-2001 |
Brian Somers <brian@FreeBSD.org> |
Do away with the ``err'' variable.
Inspired by: kris
|
#
0c50e528 |
| 02-Jul-2001 |
Kris Kennaway <kris@FreeBSD.org> |
Silence some of the -Wnon-const-format warnings and add __printflike() to a function prototype which needs it.
Approved by: brian MFC After: 2 weeks
|
#
6cf6ee76 |
| 18-Jun-2001 |
Brian Somers <brian@FreeBSD.org> |
Add support for stateful MPPE (microsoft encryption) providing encryption compatibility with Windows 2000. Stateful encryption uses less CPU but is bad on lossy transports.
The ``set mppe'' command
Add support for stateful MPPE (microsoft encryption) providing encryption compatibility with Windows 2000. Stateful encryption uses less CPU but is bad on lossy transports.
The ``set mppe'' command has been expanded. If it's used with any arguments, ppp will insist on encryption, closing LCP if the other end refuses.
Unfortunately, Microsoft have abused the CCP reset request so that receiving a reset request does not result in a reset ack when using MPPE...
Sponsored by: Monzoon Networks AG and FreeBSD Services Limited
show more ...
|
#
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>
|
Revision tags: release/4.3.0_cvs, release/4.3.0 |
|
#
03a2501a |
| 05-Apr-2001 |
Brian Somers <brian@FreeBSD.org> |
When we change the interface MTU, run through the routing table and tweak all route MTUs too.
|
#
2fc2f705 |
| 04-Feb-2001 |
Brian Somers <brian@FreeBSD.org> |
Untangle some cunfusion between the CLOSE_STAYDOWN, CLOSE_LCP and CLOSE_NORMAL meanings. CLOSE_NORMAL doesn't change the currently required state, the others do. This should stop ppp from entering
Untangle some cunfusion between the CLOSE_STAYDOWN, CLOSE_LCP and CLOSE_NORMAL meanings. CLOSE_NORMAL doesn't change the currently required state, the others do. This should stop ppp from entering DATALINK_READY when LCP shutdown doesn't end up happening cleanly.
Bump our version number to reflect this change.
show more ...
|