DORMANTno replies

Revision v1 of 3 in this series.

Revisions (3)
  1. v1 current
  2. v1 [diff vs current]
  3. v1 [diff vs current]

[PATCH 0/5 2.6.21-rc4] l2tp: introduce PPP over L2TP driver

From: James Chapman <jchapman@katalix.com>
Date: 2007-03-23 23:08:11

This patch set adds a driver for PPP over L2TP. Patches to follow.

The implementation uses the existing PPPoX subsystem that is currently
used only by PPPoE. A userspace daemon handles all L2TP control
protocol messages, while a PPPoX socket carries user data. The system
architecture is similar to PPPoE, where a pppd plugin uses the PPPoX
socket to send/receive PPP frames over an L2TP tunnel. PPP control
frames are delivered to pppd while data frames are handled entirely by
the kernel.

There are 5 patches in the series:-

1 - pppol2tp driver core. New code.

2 - API changes for L2TP. Adds definitions for L2TP in existing headers.

3 - Change to PPPoX core to allow PPPoX protocol modules such as
    pppol2tp to be autoloaded via modprobe.conf.

4 - Kernel makefile and config file changes.

5 - Adds an entry to MAINTAINERS file.

The driver is being used on x86, ia64, ppc, arm, mips32 and possibly
other architectures. It is also known to work on multi-core SMP boxes.

Sparse emits some warnings to do with pointer namespaces in the
msg_iov code. The same warnings are output by net/socket.c from which
some of this code is derived.

Although this driver is being actively used in various L2TP setups,
I'm sure it would benefit from review here.

--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help