From: Paul Mackerras <paulus@samba.org>
To: Jeff Mcadams <jeffm@iglou.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SyncPPP Generic PPP merge
Date: Fri, 25 May 2001 10:55:38 +1000 (EST) [thread overview]
Message-ID: <15117.44426.899390.29151@tango.paulus.ozlabs.org> (raw)
In-Reply-To: <20010524185333.B7667@iglou.com>
In-Reply-To: <002501c0e48f$ffed1e40$0c00a8c0@diemos> <E1533Ra-0005hC-00@the-village.bc.nu> <20010524185333.B7667@iglou.com>
Jeff Mcadams writes:
> Indeed. And let me just throw out another thought. A clean abstraction
> of the various portions of the PPP functionality is beneficial in other
> ways. My personal pet project being to add L2TP support to the kernel
> eventually. A good abstraction of the framing capabilities and basic
> PPP processing would be rather useful in that project.
That is exactly what ppp_generic.c is intended to do - it abstracts
out the framing and encapsulation and low-level transport of PPP
frames into ppp "channels" (see for example ppp_async.c,
ppp_synctty.c) while ppp_generic.c does the basic PPP processing
(compression, multilink, handling the network interface device etc.).
You should be able to write an L2TP channel to work with ppp_generic -
all your code would need to know about is how to take a PPP frame and
encapsulate and send it, and how to receive and decapsulate PPP
frames.
[Note to myself: send in a Documentation/ppp_generic.txt which
describes the interface between ppp_generic.c and the channels.]
> I would agree that such a project would be 2.5 material.
Do it today if you like, I can't see that adding a new PPP channel
could break anything else, it would be like adding a new driver.
Paul.
next prev parent reply other threads:[~2001-05-25 0: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
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-24 23:27 ` Paul Fulghum
2001-05-25 0:55 ` Paul Mackerras [this message]
2001-05-25 16:44 ` Jeff Mcadams
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=15117.44426.899390.29151@tango.paulus.ozlabs.org \
--to=paulus@samba.org \
--cc=jeffm@iglou.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®