From: presotto@plan9.att.com presotto@plan9.att.com
Subject: pppclient
Date: Mon, 14 Aug 1995 22:43:48 -0400 [thread overview]
Message-ID: <19950815024348.94whvzZbGaPByfxoiElCsTOo3yWuz4h7_GW0B2IjKeU@z> (raw)
I agree, we wrote a different version for brazil. Unfortunately, they
share no code except for the tcp compression. This one went out with
the release in the hope that a plan 9 version would be useful to someone.
It has worked talking to xylogics annex boxes.
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Mon Aug 14 22:42:30 EDT 1995
Received: by psuvax1.cse.psu.edu id <34220>; Mon, 14 Aug 1995 22:09:40 -0400
Received: from plan9.cs.su.oz.au ([129.78.96.2]) by psuvax1.cse.psu.edu with SMTP id <34230>; Mon, 14 Aug 1995 20:52:06 -0400
From: Boyd Roberts <boyd@plan9.cs.su.oz.au>
Date: Mon, 14 Aug 1995 19:27:36 -0400
To: 9fans@cse.psu.edu
Subject: re: pppclient
In-Reply-To: <199508140955.518.9.babip@plan9.cs.su.oz.au>
Message-ID: <199508150927.1656.9.babis@plan9.cs.su.oz.au>
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
Looking further into the IPCP code I see that its not likely
to converge when negociating with my server. The configuration
request/nak/reject code is just wrong. I'm not going to try
and fix it any further. It just doesn't hold enough state
to ensure the negociation will converge; it's nearly stateless,
but not quite.
next reply other threads:[~1995-08-15 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-15 2:43 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-21 9:03 pppclient Nigel
1995-08-14 23:27 pppclient Boyd
1995-08-13 23:55 pppclient Boyd
1995-08-10 18:18 pppclient presotto
1995-08-10 2:07 pppclient Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19950815024348.94whvzZbGaPByfxoiElCsTOo3yWuz4h7_GW0B2IjKeU@z \
--to=presotto@plan9.att.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).