Methods / L4 / FIVEM
L4 · NetworkGameTCPUDPProtocol-Aware
FIVEM stress test
Replicates realistic FiveM server traffic across TCP and UDP with authentic-looking payloads, validating whether game-aware filtering can tell genuine players from emulated load.
How it works
FiveM servers typically run on port 30120 and mix TCP and UDP traffic with distinctive payload patterns. This method generates traffic that mirrors those patterns closely enough to look like real client activity, rather than a generic flood. It tests whether your game-aware or deep-packet-inspection filtering can distinguish legitimate players from emulated sessions, and whether source-legitimacy checks hold when the payloads appear authentic.
Parameters
pps600k ppsCombined TCP/UDP packet rate
duration10-600 sLength of the sustained run
dst_port30120Default FiveM server port
source_spreadmoderate to wideDistribution of emulated client sources
Run it from the CLI
retro-cli
$ retro run fivem --target 203.0.113.45 --port 443 --duration 120
FIVEM FAQ
Why emulate FiveM traffic instead of sending a generic flood?+
Game servers often filter out generic floods easily. Emulating authentic FiveM payloads across TCP and UDP tests whether protocol-aware defenses can still separate real players from realistic-looking load.
What defense does this validate?+
It checks game-aware DPI and source-legitimacy filtering on the FiveM port, showing whether your mitigation passes traffic that looks legitimate or correctly challenges unverified sessions.