FLOW-RECEIVE(1)
π flow-receive β bestie's guide to catching NetFlow packets π
okay so this is flow-receive from the flow-tools manual set, section 1, and it's genuinely one of those little utilities that just works and nobody gives it credit for. sit down, grab a strawberry, let's get into it π
β¨ NAME β¨
flow-receive β receive flow data with the NetFlow protocol.
like, it catches flows. NetFlow ones. that's the whole vibe. π¦
β¨ SYNOPSIS β¨
flow-receive [ -h ] [ -b big|little ] [ -C comment ] [ -d debug_level ]
[ -o output_file ] [ -S stat_interval ] [ -V pdu_version ]
[ -z z_level ] localip/remoteip/port
β¨ DESCRIPTION β¨
so flow-receive is the utility that receives flows in NetFlow format. that's it, that's the job, and it slays at it. π
here's the tea on how it decides what to accept, because this part is actually important, no cap:
- when the remoteip is configured, only flows from that exporter get processed. this is the most secure and recommended configuration. do this. seriously. bestie, do this one. π«Ά
- when the localip is configured,
flow-receivewill only process flows sent to the localip IP address. - if remoteip is
0(which means "not configured"), then flows from any source IP address are accepted. like, anyone. any rando on the internet. π
also, here's a fun one: multiple non aggregated PDU versions may be accepted at once. why would you want that?? because Cisco's Catalyst 6500 NetFlow implementation exports from both the supervisor and the MSFC with the same IP address and the same port, but with different export versions. iconic, honestly. so in that situation, the exports get stored in the format specified by the -V flag β or, if you didn't set one, whichever export type is received first wins. first come first served, no fighting. β¨
β¨ OPTIONS β¨
-b big|littleβ byte order of the output. pick your endianness, live your truth. π-C Commentβ add a comment. little note to your future self, we love that.-d debug_levelβ enable debugging. turn the volume up on what's happening. π₯-hβ display help. the classic. the icon.-o fileβ write to file instead of the standard out. redirect the vibes somewhere permanent. π-S stat_intervalβ when you configure this,flow-receivewill emit a timestamped message on stderr every stat_interval minutes, telling you counters like the number of flows received, packets processed, and lost flows. it's giving checking in on you. π-V pdu_versionβ use pdu_version format for the output. here's the full menu, don't skip any, every single one is real:1β NetFlow version 1 (No sequence numbers, AS, or mask)5β NetFlow version 56β NetFlow version 6 (5+ Encapsulation size)7β NetFlow version 7 (Catalyst switches)8.1β NetFlow AS Aggregation8.2β NetFlow Proto Port Aggregation8.3β NetFlow Source Prefix Aggregation8.4β NetFlow Destination Prefix Aggregation8.5β NetFlow Prefix Aggregation8.6β NetFlow Destination (Catalyst switches)8.7β NetFlow Source Destination (Catalyst switches)8.8β NetFlow Full Flow (Catalyst switches)8.9β NetFlow ToS AS Aggregation8.10β NetFlow ToS Proto Port Aggregation8.11β NetFlow ToS Source Prefix Aggregation8.12β NetFlow ToS Destination Prefix Aggregation8.13β NetFlow ToS Prefix Aggregation8.14β NetFlow ToS Prefix Port Aggregation1005β Flow-Tools tagged version 5
-z z_levelβ configure compression level to z_level.0is disabled (no compression),9is highest compression. yes it goes both ways. yes that's a lot of squeezing. πΈ
β¨ EXAMPLES β¨
listen on port 9800 on any local interface for exports from IP address 10.0.0.1, store the exports in flows
flow-receive 0/10.0.0.1/9800 > flows
listen on port 9800 on any local interface from any IP address, display the received flows with flow-print
flow-receive 0/0/9800 | flow-print
see how the middle one is 0?? that's the "any IP address" situation. you know the one. be careful with that one. π
β¨ BUGS β¨
it is not currently possible to convert between the aggregated formats (8.x) and the non aggregated formats (1,5,6,7). so like, pick a lane. π§
β¨ AUTHOR β¨
Mark Fullmer <maf@splintered.net>
β¨ SEE ALSO β¨
and that's the whole page, bestie π this one's from the flow-tools crew, dated 26 ΠΠ²Π³ΡΡΡ 2010 β that's August 26, 2010 for those of us who don't read Cyrillic month names, and honestly? iconic of it. go catch some flows. you got this. πβ¨π¦
π¦ where this page comes from
- fedora 43: flow-tools 0.68.5.1-45.fc43 Β· LicenseRef-Callaway-BSD
- fedora 43: flow-tools 0.68.5.1-45.fc43 Β· LicenseRef-Callaway-BSD
- fedora 44: flow-tools 0.68.5.1-46.fc44 Β· LicenseRef-Callaway-BSD
- fedora 44: flow-tools 0.68.5.1-46.fc44 Β· LicenseRef-Callaway-BSD
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms