PAGES
← all tools
◆ Network Analysis & Monitoring

nfdump

v1.7.9 open-source

nfdump is a suite of tools for collecting, processing, and analyzing NetFlow, IPFIXIPFIXAn IETF standard protocol for exporting network flow records from routers and probes to a collector, giving cyber tools a vendor-neutral stream of structured traffic metadata without full packet capture., and sFlow data from network devices.

Summary

nfdump is an open-source suite of command-line tools for collecting, processing, and analyzing NetFlow, IPFIX, and sFlow data from network devices, free to use. It runs as a collector daemon (nfcapd/sfcapd) that writes flow files to disk, with the nfdump client used to filter, aggregate, and convert that data using tcpdump-like filter syntax, outputting to text, CSV, JSON, or ndjson. It suits network and security analysts who need to inspect traffic patterns or investigate incidents from flow records rather than full packet capturespacket capturesA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic., and it integrates with NfSen and with monitoring stacks via metrics export to InfluxDB or Prometheus. The project traces back to 2015 and remains active, with 62 contributors, 279 commits and 16 releases in the past year, and a last release only 26 days ago.

nfdump is a suite of tools for collecting, processing, and analyzing NetFlow, IPFIX, and sFlow data from network devices.

How nfdump helps

Which hosts talked to which other hosts, and how much traffic passed between them?

filters collected flow records by address, port, or protocol and reports matching flows with their byte and packet counts, without needing a packet capture of the traffic

Which autonomous systems are sending or receiving the most traffic on this network?

aggregates flows by source and destination ASN and produces per-AS traffic summaries

Is any of this traffic touching a Tor exit node?

enriches flow records against a Tor exit-node database so matching source or destination addresses are flagged in the output

Where geographically are these connections coming from or going to?

enriches flow records with geolocation data drawn from a GeoDB/Maxmind database and can tag the router or exporter address with its geo location in the output

Did last week's traffic pattern look different from this week's?

reads two sets of collected flow files with the same filter and aggregation and reports the matching flows from each, so the resulting byte and packet counts can be compared

How do I get flow records into a format my monitoring stack can ingest?

writes filtered or aggregated results as text, CSV, or JSON, or through a user-defined output format, instead of only its own binary layout

all 13 features, with the evidence for each →

Languages

Not documented

Features

13 capabilities across 5 capability groups · 1 backed by code, an API document or a real run

Built from nfdump's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • nfdump covers 4 of the 34 network analysis capabilities we track.
  • nfdump covers 1 of the 5 network observation capabilities we track.

What nfdump offers you

  • JSON data export2
  • Command-line interface1
Flow record export (NetFlow, IPFIX) 5 features Network analysis since 2016
File Format Support shipped Supports multiple flow data formats and output fields including IPFIX nanosecond precision. 8 releases · first seen May 2018

Shared capability: Flow record export (NetFlow, IPFIX)

release 8 total

  • Adds IPFIX nanosecond-precision time elements 156/157 (compatible with VPP 17.07) v1.7.9 · Sep 2026 · source · release history
  • Adds support for IPFIX nsec time elements 156/157 (VPP 17.07 compatible) v1.7.9 · Sep 2026 · source · release history
  • Adds -X collector option to limit stored data in nfcapd and sfcapd v1.7.2 · Apr 2023 · source · release history
  • Add biFlow direction element 239 and flow end reason element 136 to flow records. v1.6.23 · May 2021 · source · release history
  • Add reverse element enterprise ID 29305 for counter values. v1.6.23 · May 2021 · source · release history
  • Set -Tall as the default for nfcapd to collect extensions. v1.6.23 · May 2021 · source · release history
Packet Capture and Enrichment shipped Collects network flows with support for advanced packet headers, MAC/VLAN tagging, and IP geo-location. 7 releases · 1 other source · first seen Aug 2019

Shared capability: Flow record export (NetFlow, IPFIX)

release 7 total

  • Evaluate IPv6 fragmentation header and reassemble IPv6 packets v1.7.7 · Nov 2025 · source · release history
  • Implements ERSPAN protocol support in nfpcapd for capturing encapsulated traffic v1.7.2 · Apr 2023 · source · release history
  • Adds aggregation for GeoDB's enriched AS data. v1.7.1 · Dec 2022 · source · release history
  • Enables nfpcapd to automatically use TPACKET_V3 on Linux or direct BPF sockets on *BSD, adding options to collect MAC, VLAN, and first payload packet info v.1.7.0 · Sep 2022 · source · release history
  • Adds Maxmind geo-location capabilities to tag/geolocate IP addresses and AS numbers v.1.7.0 · Sep 2022 · source · release history
  • Add packet capture buffer size configuration to nfpcapd. v1.6.23 · May 2021 · source · release history

example

  • Generate nfdump netflow records directly from a network interface without external conversion nfpcapd -i eth0 -o /path/to/output/dir v1.6.18 · Aug 2019 · source
Flow Output and Formatting shipped Outputs flow data in various formats including NDJSON, hex dumps, and custom aggregation templates. 6 releases · first seen May 2018

Shared capability: Flow record export (NetFlow, IPFIX)

Also counts toward: JSON data export

release

Flow Storage and Compression shipped Stores collected flow data with support for unified compression formats and legacy format conversion. 3 releases · 3 other sources · first seen Jan 2016

Shared capability: Flow record export (NetFlow, IPFIX)

Also counts toward: Command-line interface

release

  • -z=<format> unified compression argument replacing -j/-y (supports zstd, lz4) for nfdump output. v1.7.3 · Sep 2023 · source · release history
  • Adds bzip compression switch to nfpcapd usage v1.6.16 · Nov 2017 · source · release history
  • nfdump now supports BZ2 compression alongside existing LZ0 when using the -B flag (e.g., nfdump -R /data -o json:json_bz2). v1.6.14 · Jan 2016 · source · release history

example

  • Export flow data using the new BZ2-compressed JSON format for efficient storage and transport. nfdump -R /data -o json:json_bz2 v1.6.14 · Jan 2016 · source
  • Collect flows with LZ4 compression nfcapd -z=lz4 ...
  • Convert old flow file to new format ./nfdump -r old-flowfile -y -w new-flowfile
Enterprise Vendor Support shipped Adds parsing support for specific enterprise vendors like NOKIA. 2 releases · first seen May 2021

Shared capability: Flow record export (NetFlow, IPFIX)

release

  • Add support for NOKIA enterprise in the netflow collector/parser v1.7.5 · Oct 2024 · source · release history
  • Implement element 160 (SystemInitTime) in option template and add it to Huawei flow records. v1.6.23 · May 2021 · source · release history
Traffic statistics 2 features Network analysis since 2022
Flow Aggregation and Analysis shipped Aggregates network flows by various dimensions including AS, TCP flags, IP addresses, and TTL for traffic summarization. 2 releases · 2 other sources · first seen Nov 2025

Shared capability: Traffic statistics

release

example

  • Aggregate flows by source and destination ASN to produce per-AS traffic summaries nfdump -r /flow_base_dir/router1/nfcapd.202501011200 -A srcasn,dstasn v1.7.9 · Sep 2026 · source
  • Filter and aggregate flows by IP nfdump -r flowfile 'src ip 192.0.2.1 and dst port 443' -A srcip,dstip
Metrics and Logging Integration shipped Exports flow statistics to monitoring systems via UNIX sockets and emits syslog events. 2 releases · first seen Sep 2022

Shared capability: Traffic statistics

release

  • nfprofile now emits syslog by default, supports the flush() function, and performs file verification on save. v1.7.3 · Sep 2023 · source · release history
  • Adds nfpcapd metric export feature: sends flow summary statistics to a UNIX socket every 60s for InfluxDB or Prometheus ingestion v.1.7.0 · Sep 2022 · source · release history
Packet capture (live and offline) 1 feature Network analysis since 2021
Packet Capture Protocol Support shipped Captures network packets from various protocols and interfaces including Linux nflog, OpenBSD pflog, and ERSPAN. 6 releases · 1 other source · first seen May 2021

Shared capability: Packet capture (live and offline)

release

  • Adds %gra geo-enriched router/exporter address tag with geographic info to output_raw format output v1.7.9 · Sep 2026 · source · release history
  • Adds -X <extlist> option to sfcapd to specify custom extensions v1.7.4 · Feb 2024 · source · release history
  • Supports multiple directory wildcards '@' for the -M argument v1.7.4 · Feb 2024 · source · release history
  • Adds Linux nflog capture in nfpcapd v1.7.2 · Apr 2023 · source · release history
  • Adds OpenBSD pflog format capture in nfpcapd v1.7.2 · Apr 2023 · source · release history
  • Add support for the ESP protocol in nfpcapd processed protocols list. v1.6.23 · May 2021 · source · release history

example

  • Capture sFlow records with specific custom extension fields defined in a list. sfcapd -X "flow_id,custom_metric" -i eth0 v1.7.4 · Feb 2024 · source
New protocol support (added dissectors) 1 feature Network analysis since 2020
Protocol Parsing and Decoding shipped Parses network protocols including IPv6 encapsulation, YAF files, and DNS with SPCDNS support. 5 releases · first seen Nov 2020

Shared capability: New protocol support (added dissectors)

release

Network flow analysis 1 feature Network observation since 2023
Geo-location Data Integration shipped Enriches flow data with geographical information using GeoDB, supporting updated geo info handling and JSON output formatting. 2 releases · first seen Apr 2023

Shared capability: Network flow analysis

Also counts toward: JSON data export

release

  • Adds Geo info to JSON output when using GeoDB with the json flag v1.7.2 · Apr 2023 · source · release history
  • GeoDB must be rebuilt for correct handling of updated geo info. v1.7.2 · Apr 2023 · source · release history
Other / not yet classified 3 features Features we have not matched to a capability yet. A suggested match is marked.
Flow Filtering and Identification shipped suggested Filters flows by IP and TTL parameters and identifies them using unique tokens. 7 releases · 2 other sources · first seen May 2018

Suggested capability: Display filtering. This is our guess, not confirmed.

release 7 total

  • Adds min ttl, max ttl and ttl equal filter options v1.7.6 · Apr 2025 · source · release history
  • Adds idt token (%idt) for identifying flows in output formats v1.7.6 · Apr 2025 · source · release history
  • Adds source address support for nfreplay v1.7.2 · Apr 2023 · source · release history
  • Adds >= and <= comparators for filter expressions in nfdump commands v1.6.22 · Nov 2020 · source · release history
  • Adds nip in [ <iplist> ] filter syntax for matching IP address lists v1.6.22 · Nov 2020 · source · release history
  • Add dir filter syntax equivalent to flowdir for filtering flows by direction v1.6.21 · Aug 2020 · source · release history

example

  • Match traffic involving a specific list of IPv6 IP addresses using the new nip syntax. nfdump -r flow.nf 'nip in [ 2001:db8::1, 2001:db8::2 ]' v1.6.22 · Nov 2020 · source
  • Filter flows with source ports greater than or equal to 80 and less than or equal to 443 using the new comparators. nfdump -r flow.nf 'srcport >= 80 and srcport <= 443' v1.6.22 · Nov 2020 · source
Performance Optimization shipped Optimizes processing speed through parallel execution, thread limits, and CPU instruction tuning. 6 releases · 2 other sources · first seen Sep 2023

release

  • Introduced a post-processor thread in the collector to speed up rotation cycles v1.7.8 · Apr 2026 · source · release history
  • Adds --enable-lto configure flag to enable link-time optimization v1.7.8 · Apr 2026 · source · release history
  • User-supplied worker thread count now also applies to filter threads v1.7.8 · Apr 2026 · source · release history
  • nfanon now supports -W num to request a specific number of worker threads v1.7.8 · Apr 2026 · source · release history
  • Improve performance with parallel filtering and parallel processing of reading, filtering and data v1.7.5 · Oct 2024 · source · release history
  • Config key maxworkers in nfdump.conf to limit worker thread count for nfcapd/nfreplay. v1.7.3 · Sep 2023 · source · release history

example

  • Enable link-time optimization during compilation for potential performance gains. ./configure --enable-lto v1.7.8 · Apr 2026 · source
  • Run nfanon with exactly 4 worker threads instead of the default auto-detection. nfanon -W 4 input.pcap v1.7.8 · Apr 2026 · source
Native CPU optimization builds verified Supports building with `-march=native` to enable CPU-specific instruction set tuning and vectorization for the local host processor. 2 releases · 1 other source · first seen Apr 2023

release

  • Adds --enable-native configure flag to generate locally optimized binaries v1.7.8 · Apr 2026 · source · release history
  • Implements %sasn and %dasn printing tags for source/destination AS organization names in nfcapd v1.7.2 · Apr 2023 · source · release history

command line

  • --enable-native — Use `-march=native` to enable CPU-specific optimizations for the build host. This enables vectorization and instruction set tuning based on the local processor. Recommended for local builds, not for portable binaries. v1.7.8 · Apr 2026 · command-line history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for nfdump, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail nfdump puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

24 entries

  1. September 20261
  2. July 20267
  3. April 20261
  4. November 20251
  5. April 20251
  6. October 20241
  7. February 20241
  8. September 20231
  9. April 20231
  10. December 20221
  11. September 20221
  12. May 20211
  13. November 20201
  14. August 20201
  15. August 20191
  16. May 20181
  17. November 20171
  18. January 20161
    Show

    24 entries

    Project health

    Issue, contributor and maintainer activity in phaag/nfdump, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 3 −5 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 89% of issues opened, last 12 months
    5. Median time to close 5 days first maintainer reply 18 hours
    6. Open backlog 4 of 507 issues ever filed
    1. Issues opened / month 1 · 1 communitymaintainers
    2. Open backlog 4
    3. Contributors / month 1
    4. Commits / month 7
    5. Stars 920
    Issue themes, last 12 months
    • bugs 17%
    • features 22%
    • questions 17%
    • other 44%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →