Skip to content
Official Xelerance fork of L2TPd
C
Pull request Compare This branch is 151 commits behind xelerance:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
contrib
debian
doc
examples
packaging
scripts
.gitignore
BUGS
CHANGES
CREDITS
LICENSE
Makefile
README.xl2tpd
TODO
aaa.c
aaa.h
avp.c
avp.h
avpsend.c
call.c
call.h
common.h
control.c
control.h
file.c
file.h
ipsecmast.h
l2tp.h
md5.c
md5.h
misc.c
misc.h
network.c
osport.h
pty.c
scheduler.c
scheduler.h
tags
xl2tpd-control.c
xl2tpd.c

README.xl2tpd

URL         : http://www.xelerance.com/software/xl2tpd/
Summary     : Layer 2 Tunnelling Protocol Daemon (RFC 2661)
Description :
xl2tpd is an implementation of the Layer 2 Tunnelling Protocol (RFC 2661).
L2TP allows you to tunnel PPP over UDP. Some ISPs use L2TP to tunnel user
sessions from dial-in servers (modem banks, ADSL DSLAMs) to back-end PPP
servers. Another important application is Virtual Private Networks where
the IPsec protocol is used to secure the L2TP connection (L2TP/IPsec,
RFC 3193). The L2TP/IPsec protocol is mainly used by Windows and
Mac OS X clients. On Linux, xl2tpd can be used in combination with IPsec
implementations such as Openswan.
Example configuration files for such a setup are included in this RPM.

xl2tpd works by opening a pseudo-tty for communicating with pppd.
It runs completely in userspace but supports kernel mode L2TP. 

xl2tpd supports IPsec SA Reference tracking to enable overlapping internak
NAT'ed IP's by different clients (eg all clients connecting from their
linksys internal IP 192.168.1.101) as well as multiple clients behind
the same NAT router.

xl2tpd supports the pppol2tp kernel mode operations on 2.6.23 or higher,
or via a patch in contrib for 2.4.x kernels. Note that kernel mode and
IPsec SA Reference tracking do not yet work together.

Xl2tpd is based on the 0.69 L2TP by Jeff McAdams <jeffm@iglou.com>
It was de-facto maintained by Jacco de Leeuw <jacco2@dds.nl> in 2002 and 2003.

Something went wrong with that request. Please try again.