netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Chapman <jchapman@katalix.com>
To: netdev@vger.kernel.org
Subject: L2TP support?
Date: Thu, 22 Mar 2007 16:09:09 +0000	[thread overview]
Message-ID: <4602AA25.6020001@katalix.com> (raw)

Is there interest in adding L2TP support?

I have a patch which could be submitted for review. The PPPoL2TP driver
presents a PPPoX socket to userspace pppd in the same way as the PPPoE
and PPPoATM drivers. The kernel handles all data traffic, while
userspace daemons do L2TP and PPP control message processing.

I posted an initial version of the patch in Sept 2004 (!). There was
some discussion about the use of PPPoX for L2TP in the following thread:

http://marc.info/?l=linux-netdev&m=109571479604766&w=2

In that thread, I was asked to improve the scalability of my solution by
avoiding the socket-per-session usage imposed by the PPPoX model. I
spent some time on this but was unable to come up with a better solution
than the original. Since then, the original PPPoX-based solution has
matured and is now use successfully by more than one L2TP protocol
implementation. My original work has been kept up to date with the
current kernel so could be submitted again if people want it. I didn't
want to repost it without revisiting the above thread first though... :)

Shall I post the patch?

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development





             reply	other threads:[~2007-03-22 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 16:09 James Chapman [this message]
2007-03-22 17:33 ` L2TP support? Ingo Oeser
2007-03-22 20:13   ` James Chapman
2007-03-23  7:05     ` Jorge Boncompte [DTI2]

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=4602AA25.6020001@katalix.com \
    --to=jchapman@katalix.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).