Methods / L4 / OVH-TCP
L4 · NetworkTCPChainEvasiveMitigation-Test
OVH-TCP stress test
Runs a multi-stage TCP chain tuned to probe whether OVH-style network mitigations actually hold on your hosted IP.
How it works
This method sends a crafted TCP chain whose packet timing, flags, and sequencing are tuned to resemble traffic that generic filters tend to pass, making it a realistic test of a hardened provider's scrubbing. It is built specifically to stress the mitigation profile common to OVH and similar networks. Use it on infrastructure you host there to verify that the provider's filtering, your firewall rules, and any custom mitigation policy still catch sophisticated TCP-layer floods rather than only obvious ones.
Parameters
portany TCP portDestination service port under test.
pps600k ppsAggregate packet rate across the chain.
duration10-300 sTest runtime.
sourcesdistributed rangesSource spread to emulate a multi-origin flood.
Run it from the CLI
retro-cli
$ retro run ovh-tcp --target 203.0.113.45 --port 443 --duration 120
OVH-TCP FAQ
Is OVH-TCP testing legal?+
Only against infrastructure you own or are authorized to test. RETRO//STRESS requires authorized targets.
What does OVH-TCP stress?+
Runs a multi-stage TCP chain tuned to probe whether OVH-style network mitigations actually hold on your hosted IP.
Can I combine it with other methods?+
Yes, add it as a step in a packet chain to sequence it with other protocols.