All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Chapman <jchapman@katalix.com>
To: Ingo Oeser <netdev@axxeo.de>
Cc: netdev@vger.kernel.org
Subject: Re: L2TP support?
Date: Thu, 22 Mar 2007 20:13:40 +0000	[thread overview]
Message-ID: <4602E374.4010802@katalix.com> (raw)
In-Reply-To: <200703221833.33530.netdev@axxeo.de>

Hi Ingo,

Ingo Oeser wrote:
> Hi James,
> 
> James Chapman schrieb:
>> Is there interest in adding L2TP support?
> 
> Yes, if there is also a user space part somewhere.

Yes there is. There's a pppd plugin which comes with the openl2tp 
project, http://sf.net/projects/openl2tp. OpenL2TP supports both LAC and 
LNS operation. A patch is also available to allow this driver to be used 
with another L2TP implementation, l2tpd.

>> 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.
> 
> Like the pppoe-plugin for pppd? 

Yes. :) The plan is to submit the pppol2tp plugin for pppd for inclusion 
in the pppd distro after the kernel driver is integrated.

> Yes, please check your patch using the nice checklist in 
> Documentation/SubmitChecklist and do it in suitable chunks 
> according to Documentation/SubmittingPatches

Will do.

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



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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 16:09 L2TP support? James Chapman
2007-03-22 17:33 ` Ingo Oeser
2007-03-22 20:13   ` James Chapman [this message]
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=4602E374.4010802@katalix.com \
    --to=jchapman@katalix.com \
    --cc=netdev@axxeo.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.