10 Commits

Author SHA1 Message Date
cwen
412e892842 fastnetmon: use __atomic* primitives instead of __sync* ones
This fixes the build on macppc, and probably hppa.

OK naddy@ jasper@ (maintainer)
2019-10-09 23:12:39 +00:00
sthen
48b0b9660c replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes 2019-07-12 20:48:23 +00:00
jasper
df4c1593e1 update to fastnetmon-1.1.4 2019-04-01 03:53:04 +00:00
sthen
49b00025fd bump REVISION for ports with a LIB_ or RUN_DEPENDS on devel/boost,
it has been split into subpackages
2018-12-13 19:53:23 +00:00
sthen
25f0e460f2 Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.

This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -

- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.

- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.

devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
2018-10-24 14:27:57 +00:00
espie
f4b7f81318 convert to PKGSTEM 2018-09-04 12:46:09 +00:00
jasper
21da44f213 this bit got merged upstream too 2018-07-12 12:56:30 +00:00
jasper
7f4821dd18 merged upstream 2018-07-12 06:27:07 +00:00
ajacoutot
dde558d1d4 PREFIX -> TRUEPREFIX 2018-07-11 15:24:56 +00:00
jasper
35f97ff1b7 import fastnetmon-1.1.3 (git HEAD really)
FastNetMon is a very high performance DDoS detector built on top of
multiple packet capture engines: NetFlow, IPFIX, sFLOW.

It could detect malicious traffic in your network and immediately block
it with BGP blackhole or BGP flow spec rules.

It has solid support for all top network vendors and has unlimited
scalability due to flexible design.

tested with pflow(4)
ok aja@
2018-07-11 15:16:47 +00:00