From: "Paul Fulghum" <paulkf@microgate.com>
To: <rjd@xyzzy.clara.co.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: SyncPPP IPCP/LCP loop problem and patch
Date: Thu, 24 May 2001 10:56:11 -0600 [thread overview]
Message-ID: <003b01c0e472$6f7a3ae0$0c00a8c0@diemos> (raw)
In-Reply-To: <200105241530.f4OFUdw27786@xyzzy.clara.co.uk>
From: <rjd@xyzzy.clara.co.uk>
> Linux syncppp does not have a LCP_STATE_REQ_SENT ...
[snip]
> Who's the owner for syncppp.c ? I might be able to put some time in on
> it, but would hate to be sending patches into empty space.
I'm not sure anyone is willing to claim ownership :)
I did not realize that syncppp does not implement
all the RFC1661 states. That's simply broken :(
A proper state machine implementation would be nice.
On the other hand, it works in a minimal way
for most people and it's supposed to be folded
into the generic PPP implementation someday.
So there's not much point in trying to overhaul the code.
Paul Fulghum paulkf@microgate.com
Microgate Corporation www.microgate.com
next prev parent reply other threads:[~2001-05-24 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 10:51 SyncPPP IPCP/LCP loop problem and patch rjd
2001-05-22 12:31 ` Paul Mackerras
2001-05-22 13:34 ` rjd
2001-05-22 16:11 ` Paul Fulghum
2001-05-24 15:11 ` SyncPPP IPCP/LCP loop problem and patch. Take 2 rjd
2001-05-22 18:13 ` SyncPPP IPCP/LCP loop problem and patch Paul Fulghum
2001-05-24 15:30 ` rjd
2001-05-24 16:56 ` Paul Fulghum [this message]
2001-05-24 18:13 ` Alan Cox
2001-05-24 20:27 ` SyncPPP Generic PPP merge Paul Fulghum
2001-05-24 22:18 ` Alan Cox
2001-05-24 22:53 ` Jeff Mcadams
2001-05-25 0:55 ` Paul Mackerras
2001-05-25 16:44 ` Jeff Mcadams
2001-05-24 23:27 ` Paul Fulghum
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='003b01c0e472$6f7a3ae0$0c00a8c0@diemos' \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjd@xyzzy.clara.co.uk \
/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