./net/xl2tpd [l2tp client/server]
[+] Add this package to your ports tracker

[ CVSweb ] [ Homepage ] [ RSS feed ]

Version: 1.3.8, Package name: xl2tpd-1.3.8
Maintained by: The OpenBSD ports mailing-list
Master sites:
Description
xl2tpd is an implementation of the Layer 2 Tunnelling Protocol (RFC 2661),
which works by opening a pseudo-tty for communicating with pppd.

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).


Filesize: 498.07 KB
Version History (View Complete History)
  • (2016-11-14) Updated to version: xl2tpd-1.3.8
  • (2013-01-16) Package added to openports.se, version xl2tpd-1.3.1 (created)
[show/hide] View available PLISTS (Can be a lot of data)

CVS Commit History:

   2017-06-25 04:31:47 by Landry Breuil | Files touched by this commit (3)
Log message:
Update to xl2tpd 1.3.9.
ok sthen@
   2017-06-25 04:31:47 by Landry Breuil | Files touched by this commit (3)
Log message:
Update to xl2tpd 1.3.9.
ok sthen@
   2017-06-25 04:31:47 by Landry Breuil | Files touched by this commit (3)
Log message:
Update to xl2tpd 1.3.9.
ok sthen@
   2017-05-06 09:10:18 by Marc Espie | Files touched by this commit (68)
Log message:
adjust distinfo post DISTFILES change
   2016-11-21 07:19:48 by Stuart Henderson | Files touched by this commit (1)
Log message:
drop maintainer, I'm not using xl2tpd any more
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2016-11-14 02:35:38 by Landry Breuil | Files touched by this commit (8)
Log message:
Update to xl2tpd 1.3.8, xelerance switched to github.
Most of our patches merged upstream, and while here remove a -Os from
CFLAGS (spotted by jca@). With this update, i've (finally!) been able to
connect to an OpenBSD VPN running isakmpd with psk/npppd.
ok sthen@ (MAINTAINER)
   2015-06-19 10:34:41 by Stuart Henderson | Files touched by this commit (6)
Log message:
Add a fix from Sergey Ryazanov <ryazanov.s.a / gmail.com> to handle
fragmented ppp frames while reading from pty. From Sergey's mail:
=====
xl2tpd could not correctly handle fragmented ppp frame while read it
from pty if one of consequent read operation return an error.
That's happening because xl2tpd too often cleans the buffer and
assumes that each read frame operation is performed for new frame,
since xl2tpd uses single buffer for pty and for socket read operations.
The attached patch moves all pty related buffers into _call_ context
and corrects calculation of buffer position, what fixes issue with
handling of fragmented frames. Now we can use MTU > 1000. I tested
these changes with load (L2TP tunnel without IPSec) and all seems work
normally. No more "Protocol-Reject" frames.
=====
Performance is still poor (Sergey was seeing ~2Mb/s, I am seeing less
despite low cpu use) but the tunnel now seems reliable.
   2015-06-19 10:34:41 by Stuart Henderson | Files touched by this commit (6)
Log message:
Add a fix from Sergey Ryazanov <ryazanov.s.a / gmail.com> to handle
fragmented ppp frames while reading from pty. From Sergey's mail:
=====
xl2tpd could not correctly handle fragmented ppp frame while read it
from pty if one of consequent read operation return an error.
That's happening because xl2tpd too often cleans the buffer and
assumes that each read frame operation is performed for new frame,
since xl2tpd uses single buffer for pty and for socket read operations.
The attached patch moves all pty related buffers into _call_ context
and corrects calculation of buffer position, what fixes issue with
handling of fragmented frames. Now we can use MTU > 1000. I tested
these changes with load (L2TP tunnel without IPSec) and all seems work
normally. No more "Protocol-Reject" frames.
=====
Performance is still poor (Sergey was seeing ~2Mb/s, I am seeing less
despite low cpu use) but the tunnel now seems reliable.
   2015-06-19 10:34:41 by Stuart Henderson | Files touched by this commit (6)
Log message:
Add a fix from Sergey Ryazanov <ryazanov.s.a / gmail.com> to handle
fragmented ppp frames while reading from pty. From Sergey's mail:
=====
xl2tpd could not correctly handle fragmented ppp frame while read it
from pty if one of consequent read operation return an error.
That's happening because xl2tpd too often cleans the buffer and
assumes that each read frame operation is performed for new frame,
since xl2tpd uses single buffer for pty and for socket read operations.
The attached patch moves all pty related buffers into _call_ context
and corrects calculation of buffer position, what fixes issue with
handling of fragmented frames. Now we can use MTU > 1000. I tested
these changes with load (L2TP tunnel without IPSec) and all seems work
normally. No more "Protocol-Reject" frames.
=====
Performance is still poor (Sergey was seeing ~2Mb/s, I am seeing less
despite low cpu use) but the tunnel now seems reliable.
   2015-06-19 10:34:41 by Stuart Henderson | Files touched by this commit (6)
Log message:
Add a fix from Sergey Ryazanov <ryazanov.s.a / gmail.com> to handle
fragmented ppp frames while reading from pty. From Sergey's mail:
=====
xl2tpd could not correctly handle fragmented ppp frame while read it
from pty if one of consequent read operation return an error.
That's happening because xl2tpd too often cleans the buffer and
assumes that each read frame operation is performed for new frame,
since xl2tpd uses single buffer for pty and for socket read operations.
The attached patch moves all pty related buffers into _call_ context
and corrects calculation of buffer position, what fixes issue with
handling of fragmented frames. Now we can use MTU > 1000. I tested
these changes with load (L2TP tunnel without IPSec) and all seems work
normally. No more "Protocol-Reject" frames.
=====
Performance is still poor (Sergey was seeing ~2Mb/s, I am seeing less
despite low cpu use) but the tunnel now seems reliable.
   2015-06-19 10:34:41 by Stuart Henderson | Files touched by this commit (6)
Log message:
Add a fix from Sergey Ryazanov <ryazanov.s.a / gmail.com> to handle
fragmented ppp frames while reading from pty. From Sergey's mail:
=====
xl2tpd could not correctly handle fragmented ppp frame while read it
from pty if one of consequent read operation return an error.
That's happening because xl2tpd too often cleans the buffer and
assumes that each read frame operation is performed for new frame,
since xl2tpd uses single buffer for pty and for socket read operations.
The attached patch moves all pty related buffers into _call_ context
and corrects calculation of buffer position, what fixes issue with
handling of fragmented frames. Now we can use MTU > 1000. I tested
these changes with load (L2TP tunnel without IPSec) and all seems work
normally. No more "Protocol-Reject" frames.
=====
Performance is still poor (Sergey was seeing ~2Mb/s, I am seeing less
despite low cpu use) but the tunnel now seems reliable.
   2015-06-19 10:34:41 by Stuart Henderson | Files touched by this commit (6)
Log message:
Add a fix from Sergey Ryazanov <ryazanov.s.a / gmail.com> to handle
fragmented ppp frames while reading from pty. From Sergey's mail:
=====
xl2tpd could not correctly handle fragmented ppp frame while read it
from pty if one of consequent read operation return an error.
That's happening because xl2tpd too often cleans the buffer and
assumes that each read frame operation is performed for new frame,
since xl2tpd uses single buffer for pty and for socket read operations.
The attached patch moves all pty related buffers into _call_ context
and corrects calculation of buffer position, what fixes issue with
handling of fragmented frames. Now we can use MTU > 1000. I tested
these changes with load (L2TP tunnel without IPSec) and all seems work
normally. No more "Protocol-Reject" frames.
=====
Performance is still poor (Sergey was seeing ~2Mb/s, I am seeing less
despite low cpu use) but the tunnel now seems reliable.
   2015-01-08 07:08:15 by Antoine Jacoutot | Files touched by this commit (4)
Log message:
Fix rcctl(8) usage.
   2015-01-08 07:08:15 by Antoine Jacoutot | Files touched by this commit (4)
Log message:
Fix rcctl(8) usage.