Methods / L4 / UDP-CUSTOM
L4 · NetworkVolumetricUDPConfigurableSpoofable

UDP-CUSTOM stress test

Floods your target with UDP packets you define byte for byte, validating how filters react to arbitrary payloads and protocol-shaped traffic.

How it works

This method emits UDP datagrams whose contents you control: a custom hexadecimal payload and an adjustable packet size. By shaping the bytes to resemble a real application protocol, you can test whether deep-packet-inspection rules, payload signatures, and per-protocol rate limits hold up against traffic that does not match a generic flood template. It is the most flexible UDP vector for reproducing a specific attack profile you have observed against your own infrastructure.

Parameters

Packet rate600k ppsDatagrams emitted per second per source thread
Payload bytes1-1472 bytesLength of the custom payload before fragmentation
Payload patternhex stringExact byte sequence to place in each datagram
Duration10-600 sTest window length

Run it from the CLI

retro-cli
$ retro run udp-custom --target 203.0.113.45 --port 443 --duration 120

UDP-CUSTOM FAQ

Is UDP-CUSTOM testing legal?+
Only against infrastructure you own or are authorized to test. RETRO//STRESS requires authorized targets.
What does UDP-CUSTOM stress?+
Floods your target with UDP packets you define byte for byte, validating how filters react to arbitrary payloads and protocol-shaped traffic.
Can I combine it with other methods?+
Yes, add it as a step in a packet chain to sequence it with other protocols.