From: Chris Dukes <pakrat@www.uk.linux.org>
To: fabrizio.gennari@philips.com
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: PPP over socket?
Date: Sat, 12 Jan 2002 01:12:07 +0000 [thread overview]
Message-ID: <20020112011207.F7199@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <OF89E28C88.FEBD33E7-ONC1256B3E.002E62B6@diamond.philips.com>
In-Reply-To: <OF89E28C88.FEBD33E7-ONC1256B3E.002E62B6@diamond.philips.com>; from fabrizio.gennari@philips.com on Fri, Jan 11, 2002 at 10:13:57AM +0100
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.
--
Chris Dukes
"Bert is apparently EEEEVIL, whereas Oscar is just a sysadmin^Wgrouch."
-- gorski
next parent reply other threads:[~2002-01-12 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF89E28C88.FEBD33E7-ONC1256B3E.002E62B6@diamond.philips.com>
2002-01-12 1:12 ` Chris Dukes [this message]
2002-01-12 1:44 ` PPP over socket? J Sloan
2002-01-12 2:17 Jean Tourrilhes
-- strict thread matches above, loose matches on Subject: below --
2002-01-14 9:07 fabrizio.gennari
2002-01-14 17:28 ` Jean Tourrilhes
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=20020112011207.F7199@parcelfarce.linux.theplanet.co.uk \
--to=pakrat@www.uk.linux.org \
--cc=fabrizio.gennari@philips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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