nfsen-ng-nfcapd ghcr.io/mbolli/nfsen-ng:latest https://github.com/mbolli/nfsen-ng/pkgs/container/nfsen-ng bridge bash false https://github.com/mbolli/nfsen-ng/issues https://github.com/mbolli/nfsen-ng NetFlow / sFlow / IPFIX collector (nfcapd) for nfsen-ng. It runs the nfcapd daemon from the nfsen-ng image, listening on a UDP port and writing rotated flow files that the nfsen-ng web UI reads. Point your router/switch flow exporter (pfSense/OPNsense/MikroTik/…) at this host on the collector port (default 9995/UDP). Mount this container on the SAME appdata path as the nfsen-ng UI, and make sure the write directory's last path segment (default "flows") matches one of the UI's Sources. This container has no web interface. Network:Management Tools: Status:Stable https://raw.githubusercontent.com/mbolli/nfsen-ng/master/deploy/unraid/nfsen-ng-nfcapd.xml https://raw.githubusercontent.com/mbolli/nfsen-ng/master/deploy/unraid/nfsen-ng-icon.png --restart unless-stopped --entrypoint /usr/local/nfdump/bin/nfcapd -w /data/nfsen-ng/live/flows -z=lz4 -S 1 -T all -p 9995 Buy the maintainer a beer https://paypal.me/bolli Install the nfsen-ng UI template too, and mount both containers on the SAME data path (default /mnt/user/appdata/nfsen-ng). The last segment of the write path (-w .../live/<name>, default "flows") must match one of the UI's NFSEN_SOURCES. A device on your network must export flows to this host's collector UDP port. 9995 /mnt/user/appdata/nfsen-ng UTC