Methods / L4 / CHAIN
L4 · NetworkLayer 4Mixed ProtocolSequencedEvasive
CHAIN stress test
Runs a scripted sequence of packet stages back to back so you can test how mitigation reacts to a flood whose shape keeps changing.
How it works
A chain method strings together several distinct traffic stages and plays them in sequence, instead of repeating one fixed packet over and over. As the pattern shifts, signature-based and static-threshold defenses have to keep re-deciding what to block, which exposes filters that only catch a single steady flood shape. It is a controlled way to check that your layered mitigation adapts rather than relying on one rule that a varying attack would slip past.
Parameters
stages2-8 stagesNumber of sequenced traffic phases in the chain.
pps600k ppsAggregate packet rate across the active stage.
duration30-300 sTotal run covering the full stage sequence.
sources1-manySpread of source addresses applied across stages.
Run it from the CLI
retro-cli
$ retro run chain --target 203.0.113.45 --port 443 --duration 120
CHAIN FAQ
Is CHAIN testing legal?+
Only against infrastructure you own or are authorized to test. RETRO//STRESS requires authorized targets.
What does CHAIN stress?+
Runs a scripted sequence of packet stages back to back so you can test how mitigation reacts to a flood whose shape keeps changing.
Can I combine it with other methods?+
Yes, add it as a step in a packet chain to sequence it with other protocols.