flowgrindd(1)
π flowgrindd(1) β the Flowgrind Manual, bestie edition π
okay so real quick, this is the page for flowgrindd, and if you're reading this you're probably about to spin up some network measurement chaos. so proud of you. π«Ά
β¨ NAME β¨
flowgrindd β advanced TCP traffic generator for Linux, FreeBSD, and Mac OS X π
no cap, that's literally the whole name. it's giving main character energy for your network stack.
πΈ SYNOPSIS πΈ
flowgrindd [OPTION]...
that's it. that's the whole vibe. options go in, daemon comes out. β¨
π¦ DESCRIPTION π¦
so flowgrindd is the daemon for the advanced TCP traffic generator flowgrind(1). like, it's the quiet one in the group chat that does the actual work while everyone else is typing. π
using the flowgrind(1) controller, you can set up distributed network performance measurement tests between an arbitrary number of hosts running flowgrindd, the flowgrind daemon. yes bestie, an arbitrary number. go feral. π
π OPTIONS π
okay so first thing first, a lil rule:
mandatory arguments to long options are mandatory for short options too. the way that means something. π
here's every single one, no skipping, we don't do that here:
-bADDR β XML-RPC server bind address. and listen, an easy way to enable support for IPv6 control-connections is to specify the IPv6 wildcard address"::". that's the whole trick. iconic. π-c# β bound daemon to specific CPU. first CPU is0, so don't come in here starting at 1 like a menace. β-dβ don't fork into background, increase debugging verbosity. and the way you can add this option multiple times to increase the verbosity?? stackable. obsessed. π₯-h,--helpβ display this help and exit. the classic. the beloved. π-p# β XML-RPC server port. yes, a number. pick one. πΈ-wDIR β target directory for dump files. β οΈ this one requires compiling flowgrind with libpcap support, and the daemon must be run as root. so like, real talk, be careful with this one, root is not a vibe to throw around casually. π-v,--versionβ print version information and exit. short, sweet, slays. β¨
π AUTHORS π
history lesson time, stay with me:
- Flowgrind was originally started by Daniel Schaffrath. the OG. the blueprint. π«Ά
- the distributed measurement architecture and advanced traffic generation were later on added by Tim Kosse and Christian Samsel. ate. π
- currently, flowgrind is developed and maintained by Arnd Hannemann and Alexander Zimmermann. legends fr fr. β
π BUGS π
the development and maintenance of flowgrind is primarily done via github <https://github.com/flowgrind/flowgrind>.
please report bugs via the issue webpage <https://github.com/flowgrind/flowgrind/issues>.
not me telling you to file an issue instead of just suffering in silence. communication is hot. π
π SEE ALSO π
go read those too, bestie, the lore is connected. π§
and that's the page!! π this was Flowgrind Manual energy, dated March 2014, and yeah, the header up top said flowgrindd(1) the whole time β you already knew. periodt. π
π¦ where this page comes from
- debian bookworm: flowgrind 0.8.2-2+b2
- debian trixie: flowgrind 0.8.2-2+b4
- opensuse-leap 16.0: flowgrind 0.8.2-bp160.1.13 Β· GPL-2.0-only
- opensuse-leap 16.0: flowgrind 0.8.2-bp160.1.13 Β· GPL-2.0-only
- opensuse-leap 16.0: flowgrind 0.8.2-bp160.1.13 Β· GPL-2.0-only
- opensuse-leap 16.0: flowgrind 0.8.2-bp160.1.13 Β· GPL-2.0-only
- ubuntu jammy: flowgrind 0.8.2-2build1
- ubuntu noble: flowgrind 0.8.2-2build3
- ubuntu questing: flowgrind 0.8.2-2build4
- ubuntu resolute: flowgrind 0.8.2-2build5
- ubuntu stonking: flowgrind 0.8.2-2build5
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms