l2tpd is an implementation of the layer two tunneling protocol. It works in
user space completely (although kernel work is planned after the userspace
version is stablized). l2tpd works by opening a pseudo-tty for communicating
with pppd(8).
===> The following configuration options are available for l2tpd-0.69_13:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
net/l2tpd: Fix build with GCC 14
GCC 14 has transformed some warnings into errors: revert them to simple
warnings.
PR: 281243
Reported by: exp-run (antoine)
all: R eturn sobomax' ports to the pool
Commit bit of sobomax@ was safe-kept on 2018-12-03 by portmgr-secretary@
but somehow the ports were not reset. Reset all the ports except
net/ortp which has been exclusively requested by zirias@
Approved by: portmgr (blanket)
net/l2tpd: Unbreak build with GCC 10 (-fno-common default)
/usr/local/bin/ld: pty.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: misc.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: control.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: avp.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: call.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: network.o:(.bss+0x140): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: avpsend.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: scheduler.o:(.bss+0x8): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: file.o:(.bss+0x228): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: aaa.o:(.bss+0x0): multiple definition of `rand_source';
l2tpd.o:(.bss+0x530): first defined here
/usr/local/bin/ld: control.o: in function `handle_special':
control.c:(.text+0x220e): undefined reference to `check_control'
/usr/local/bin/ld: control.o: in function `handle_packet':
control.c:(.text+0x22d0): undefined reference to `check_payload'
/usr/local/bin/ld: control.c:(.text+0x22e6): undefined reference to
`expand_payload'
/usr/local/bin/ld: control.c:(.text+0x231a): undefined reference to
`check_control'
/usr/local/bin/ld: control.c:(.text+0x2414): undefined reference to
`write_packet'
http://package18.nyi.freebsd.org/data/121amd64-default-PR244494/2020-06-10_18h04m44s/logs/errors/l2tpd-0.69_10.log
PR: 246700
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
For ports that are marked BROKEN on armv6, and also fail to build on
armv7, mark them so.
This is part two of a multipart commit to bring armv7 ports to parity
with armv6.
Approved by: portmgr (tier-2 blanket)
Obtained from: lonesome.com -exp run
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
Bump PORTREVISIONS for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
Remove indefinite articles and trailing periods from COMMENT, plus minor
COMMENT typos and surrounding whitespace fixes. A few Makefiles where not
included as they contain Latin-1 characters that break the Phabricator
workflow. Category N.
CR: D307
Approved by: portmgr (bapt)
When l2tpd(8) runs on a multi-homed machine, and you attempt to
establish an L2TP VPN connection to its external IP address from
the Windows XP box on your LAN, l2tpd(8) will reply (UDP) from
its local IP address, and not external IP address.
Implement the new global option "address" to aid in overcoming
this problem. Also helps in environments with complex NAT
configurations.
Bump PORTREVISION.
Approved by: sobomax
- Update to 0.69;
- fix an incompatibility, which causes daemon to eat 100% CPU even when
completely idle (ages old problem with select()'ing on FIFO without
writers opened for reading in non-blocking mode);
- replace incomplete and ugly daemonize code with native daemon(3).
Sponsored by: United Networks of Ukraine
