| Age | Commit message (Collapse) | Author |
|---|
|
a bum name to return as 0.0.0.0... we don't want ``delete xxx''
to delete the default route when xxx doesn't resolve.
Support IP number specifications as the host when specifying
a tcp-style device (rather than *just* hostnames).
|
|
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>
|
|
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.
|
|
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.
|
|
Increase requested by: "Clement T. Cole" <clemc@echo.ccc.com>
|
|
USER is expected to be expanded.
|
|
otherwise windows clients will keep resending the
response :-/
It'd be nice if M$ would document this sort of thing !
Problem reported by: Andrzej Tobola <san@tmp.iem.pw.edu.pl>
|
|
CALLBACK protocol and end up agreeing CBCP, DTRT and go
into CBCP phase rather than mistakenly terminating as
if CBCP wasn't agreed.
Problem reported by: Alexander Dubinin <alex@nstl.nnov.ru>
|
|
Noted & partially submitted by: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
|
|
the answer.
If we later get a descriptor exception from select(), we know
that it's a tty (isatty() returns 0 after the exception on a
tty) and remember to call modem_LogicalClose().
The upshot of it all is that descriptor exceptions dont leave
the tty locked any more.
|
|
resulting NULL FILE *.
|
|
dial & login are successful.
Submitted by: Toshiomi Moriki <Toshiomi.Moriki@ma1.seikyou.ne.jp>
|
|
mode, not in -ddial and -direct.
Pointed out by: Chris Timmons <skynyrd@opus.cts.cwu.edu>
|
|
is 0.0.0.0. This isn't a problem as the sticky route is still
added.
Suggested by: Chris Timmons <skynyrd@opus.cts.cwu.edu>
|
|
server-side CHAP authentication problems in the past :-/
|
|
Submitted by: Bill Fumerola <billf@FreeBSD.org>
|
|
Problem reported by: Christopher Hall <hsw@acm.org>
|
|
|
|
|
|
|
|
Remove any dial timer that might be hanging around at
datalink_Destroy() time. This timer may be left running
after the link is closed (making sure it's not automatically
opened again too soon).
|
|
exits, it causes a select() exception.
Handle these select() exceptions on link descriptors in pretty
much the same way as loss of carrier rather than dropping out
in confusion.
|
|
|
|
various prompts signify.
|
|
Submitted by: Forgotten (sorry)
|
|
``iface clean'' is used in auto mode while there
are no active links.
|
|
response anyway. This is what Win95 does, despite it not
being documented in the cbcp spec....
Reported by: Bill <petheram@acm.org>
|
|
line and in the ``load'' & ``dial'' commands. The last
label loaded becomes the current label name.
Only require a label for -auto mode.
|
|
for our interface address. We're about to call ip_Input()
anyway, and ip_Input() does the PacketAliasIn().
Stack trace provided by: Cameron Grant <gandalf@vilnya.demon.co.uk>
|
|
- Add enable/disable proxyall to proxy arp an entire subnet
(smaller than class C)
- Add ``set {send,recv}pipe for controlling socket buffers.
- Fix the infamous ``first connection'' problem where the process
that causes an auto dial to an ISP that assigns a dynamic IP never
connects (due to the bound socket IP being changed on the tun iface).
See ``enable/disable iface-alias'' and ``iface ...'' in the man page.
- Add PROCESSID as a substitution string when running commands.
- Add ``set proctitle'' for changing argv0. You can use all the command
substitutions here too (eg ``set proctitle ppp: USER INTERFACE'').
- Add a missing untimeout as soon as the chat expect string is received
rather than waiting for the next expect to happen.
- Be less restrictive about when auth{name,key}, enddisc, shortseq and
mrru can be changed.
- Improve some diagnostics.
- Don't send a DELAY field with CBCP_NONUM messages (as per the spec).
- Emphasise how to make callback optional in the man page.
- Allow the caller to request no callback if they're allowed choose the
number anyway.
- Set our CBCP RESPONSE fsm id according to the REQ, moan if the peer
gets the response id wrong (but continue anyway).
- Shuffle the ``set ?'' output back a column so that broken terminals
that can't display 80 columns *and* a '\n' will look ok.
- If DES is compiled out, be more verbose about why CHAP 0x80 was rejected.
|
|
Pointed out by: bde@FreeBSD.org
Patched correctly by: wosch@FreeBSD.org
|
