From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
fabrizio.gennari@philips.com,
Chris Dukes <pakrat@www.uk.linux.org>
Subject: Re: PPP over socket?
Date: Fri, 11 Jan 2002 18:17:04 -0800 [thread overview]
Message-ID: <20020111181704.A15819@bougret.hpl.hp.com> (raw)
Chris Dukes wrote :
> On Fri, Jan 11, 2002 at 10:13:57AM +0100, fabrizio.gennari@philips.com wrote:
> > I was wondering whether the socket architecture could be modified in order
> > to support PPP connections over a generic socket (of type SOCK_DGRAM or
> > SOCK_SEQPACKET), by mapping each PPP packet to a socket packet. This idea
> > is not completely new: somebody raised is in the past, see for example
> > http://oss.sgi.com/projects/netdev/mail/netdev/msg00180.html or
> > http://oss.sgi.com/projects/netdev/mail/netdev/msg01127.html .
>
> vtun already provides this capability in user space.
> (See http://vtun.sourceforge.net/)
> ppp(8) on *BSD also provides this capability in user space as well.
>
> As memory serves PPPoE on Linux is partially implemented in userspace
> as is, so a partial user space solution for PPPoUDP shouldn't be that
> wretched.
And at the total opposite of the spectrum you have IrNET, as
it is implemented in kernekl 2.4.X, that pass PPP packets on an IrDA
socket in the kernel without going through the socket API. But that's
the solution only if you don't mind debugging kernel code...
BTW, I don't understand why the socket architecture would need
to be modified. You just need a user space or a kernel space wrapper.
Regards,
Jean
next reply other threads:[~2002-01-12 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 2:17 Jean Tourrilhes [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-14 9:07 fabrizio.gennari
2002-01-14 17:28 ` Jean Tourrilhes
[not found] <OF89E28C88.FEBD33E7-ONC1256B3E.002E62B6@diamond.philips.com>
2002-01-12 1:12 ` Chris Dukes
2002-01-12 1:44 ` J Sloan
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=20020111181704.A15819@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=fabrizio.gennari@philips.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pakrat@www.uk.linux.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®