NFDUMP tools support netflow v5, v7 and v9 capturing and processing.
nfcapd - netflow capture daemon.
Reads the netflow data from the network and stores the data into files.
nfdump - netflow dump.
Reads the netflow data from the files stored by nfcapd. It's syntax is similar
to tcpdump. If you like tcpdump you will like nfdump.
nfprofile - netflow profiler.
Reads the netflow data from the files stored by nfcapd. Filters the netflow
data according to the specified filter sets ( profiles ) and stores the
filtered data into files for later use.
nfreplay - netflow replay
Reads the netflow data from the files stored by nfcapd and sends it over
the network to another host.
ft2nfdump - flow-tools to nfdump - optional component
WWW: http://nfdump.sourceforge.net
===> The following configuration options are available for nfdump-devel-20070808_4:
FT2NFDUMP=off: With Flow-tools to nfdump converter
NFDUMP14=off: Enable compatbility with version 1.4
SFLOW=off: Build sflow collector daemon also
===> Use 'make config' to modify these settings
Deprecate and expire in one month.
This port is older than net-mgmt/nfdump, use that instead.
PR: ports/174043
Submitted by: wxs@
Approved by: maintainer timeout
At the moment 1385 ports use BUILD_DEPENDS= ${RUN_DEPENDS} and 450
ports use BUILD_DEPENDS:= ${RUN_DEPENDS}. This patch fixes ports that are
currently broken. This is a temporary measure until we organically stop using
:= or someone(s) spend a lot of time changing all the ports over.
Explicit duplication > := > = and this just moves ports one step to the left
Approved by: portmgr
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
First steps in a big migration:
Move net/rrdtool to databases/rrdtool.
It's an itch which needs to be scratched: net/rrdtool came from
net/mrtg, which was a good location for it. net/mrtg has later
been moved to net-mgmt/mrtg. net/rrdtool is "Round Robin Database
Tools", therefor it's better if it moves to databases/rrdtool.
Same with net/rrdtool10.
PR: ports/112942
Submitted by: Edwin Groothuis <edwin@mavetju.org>
- After repocopy, add development version of nfdump at 1.5
PR: ports/91725
Submitted by: Janos Mohacsi <janos.mohacsi@bsd.hu> (maintainer)
Repocopied by: marcus