cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
c54491d9a8
openbsd-ports/net/xl2tpd/Makefile

44 lines
1.2 KiB
Makefile
Raw Normal View History

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 12:34:41 -04:00
# $OpenBSD: Makefile,v 1.9 2015/06/19 16:34:41 sthen Exp $
import ports/net/xl2tpd, ok pirofti@ 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).
2013-01-15 18:02:19 -05:00
COMMENT= l2tp client/server
DISTNAME= xl2tpd-1.3.1
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 12:34:41 -04:00
REVISION= 6
import ports/net/xl2tpd, ok pirofti@ 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).
2013-01-15 18:02:19 -05:00
CATEGORIES= net
HOMEPAGE= http://www.xelerance.com/services/software/xl2tpd/
MAINTAINER= Stuart Henderson <sthen@openbsd.org>
# GPLv2
PERMIT_PACKAGE_CDROM= Yes
WANTLIB += c util
# https://github.com/xelerance/xl2tpd/
Add some notes on l2tp+ipsec. Definitely not perfect as there are some issues with fragments and stalls under high load, but it is possible to connect to npppd using l2tp+ipsec with this information.
2014-10-09 09:06:04 -04:00
MASTER_SITES= http://download.openswan.org/xl2tpd/
import ports/net/xl2tpd, ok pirofti@ 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).
2013-01-15 18:02:19 -05:00
FAKE_FLAGS= DESTDIR= MANDIR=${WRKINST}${PREFIX}/man
PERMIT_* / REGRESS->TEST sweep
2013-03-11 07:35:43 -04:00
NO_TEST= Yes
import ports/net/xl2tpd, ok pirofti@ 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).
2013-01-15 18:02:19 -05:00
do-configure:
perl -pi -e 's,/etc,${SYSCONFDIR},' ${WRKSRC}/file.h
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/xl2tpd/
cd ${WRKSRC}/doc; ${INSTALL_DATA} l2tpd.conf.sample \
l2tp-secrets.sample ../examples/ppp-options.xl2tpd \
${PREFIX}/share/examples/xl2tpd/
enable xl2tpd-control and adjust README
2013-03-28 14:24:29 -04:00
# Only build xl2tpd/xl2tpd-control for now; pfc A) needs something that was
# stripped from our libpcap and B) isn't useful with our old pppd anyway.
# If enabling this, these 4 lines can go.
ALL_TARGET= xl2tpd xl2tpd-control
import ports/net/xl2tpd, ok pirofti@ 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).
2013-01-15 18:02:19 -05:00
do-install:
enable xl2tpd-control and adjust README
2013-03-28 14:24:29 -04:00
${INSTALL_PROGRAM} ${WRKSRC}/xl2tpd{,-control} ${PREFIX}/sbin/
import ports/net/xl2tpd, ok pirofti@ 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).
2013-01-15 18:02:19 -05:00
${INSTALL_DATA} ${WRKSRC}/doc/*.8 ${PREFIX}/man/man8/
${INSTALL_DATA} ${WRKSRC}/doc/*.5 ${PREFIX}/man/man5/
.include <bsd.port.mk>
Reference in New Issue Copy Permalink