| Age | Commit message (Collapse) | Author |
|---|
|
correctly by invoking the timer to get the value before
displaying the message.
Don't assume that a value of 0 is ``random'' in
``show datalink''.
Make the random value between 1 and DIAL_TIMEOUT rather
than between 0 and DIAL_TIMEOUT-1
|
|
mode (when there is more than one auto link) if there is
no data queued to go out.
Reviewed by: Tom Torrance <tom@tomqnx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
battery life falls below machdep.apmwarn
|
|
|
|
Some CHAP implementations send no welcome message with their
SUCCESS/FAILURE packets. This was being mis-identified as
a truncated packet by the new authentication code :-(
|
|
packets before dropping them in the bit-bucket.
|
|
|
|
chap 0x80.
|
|
authenticator and authenticatee.
|
|
to DATALINK_LCP.
|
|
source address to be a non-local address
|
|
|
|
|
|
is complete before checking carrier. If it's there,
the device supports carrier. If it's not it doesn't.
Add the ``set cd'' command for deciding how soon to check
for carrier, and for deciding if carrier is REQUIRED.
The default has changed: Pre 2.0 versions of ppp waited
for 1 second. Version 2 didn't wait, but this causes
problems with some (few?) modems that don't assert carrier
immediately on reporting CONNECT. The one second delay
is back now and can be removed with ``set cd 0''.
Bump the ppp version number in case this needs to be changed
again....
|
|
|
|
Mention more rfc numbers.
Don't ``.Nm Ppp'' (just use ``.Nm'').
|
|
|
|
script, expand words in the same way as !bg does.
|
|
|
|
|
|
|
|
each time rather than making up a new one.
Increase the authname/authkey max sizes to 100 characters.
Allow ``authkey'' specifications beginning with ``!''.
When a challenge is received, the text following the
``!'' is executed as a program (expanding stuff in the same
way that ``sh'' and ``!bg'' do). The program is passed the
peer name, peer challenge and local ``authname'' on standard
input and is expected to output the name/key combination that
should be used to build the CHAP response.
This provides support for Secure ID cards (guess what I was
given at work recently!) using CHAP.
Examples will follow.
|
|
|
|
(broken with last commit).
|
|
|
|
While I'm in there, validate pap & chap header IDs if
``idcheck'' is enabled (the default) for other FSM packet
types.
NOTE: This involved integrating the generation of chap
challenges and the validation of chap responses
(and commenting what's going on in those routines).
I currently have no way of testing ppps ability
to respond to M$Chap CHALLENGEs correctly, so if
someone could do the honours, it'd be much
appreciated (it *looks* ok!).
Sponsored by: Internet Business Solutions Ltd., Switzerland
|
|
|
|
|
|
|
|
item is scheduled rather than interrupting 10 times per second
and finding that there's nothing to do most of the time.
This change reduces interrupt overheads but will expose any
(previously small) latency problems.
Be more careful about building VJ compression requests - we
can't htonl/ntohl the entire four bytes ! Also, when we get
a NAK, try to get as close as possible to what the peer NAKs
with when sending our next REQ. Similarily when we send a NAK,
pick values as close as possible to what the peer REQd.
Fix a couple of man page typos (compliments of billf@FreeBSD.org)
|
|
|
|
|
|
|
|
the command line.
Revise the error diagnostics so that invalid labels
are reported immediately.
|
|
at the authentication layer rather than at the PAP layer
so that it also applies to CHAP (no response to CHAP
challenges).
|
|
|
|
requests, give up (don't sit there indefinitely).
|
|
|
|
section.
Submitted by: Dan Lukes <dan@obluda.cz>
|
|
|
|
|
|
|
|
got an open link, we want it to be select()d on - otherwise
we get a freeze when ``openmode'' is passive.
|
