ICMP echo flood
Ping-like ICMP echo requests at high rate. Tests network device CPU, ICMP rate limits, and upstream provider policies.
How it works
- Echo request (Type 8) expects echo reply (Type 0) from the target or edge.
- Devices must process control-plane traffic alongside data-plane load.
- Some providers filter ICMP aggressively; simulation clarifies what reaches your asset.
Packet flow (illustrative)
Engarde node Target
→ICMP Echo RequestType 8
←ICMP Echo ReplyType 0
→Echo Request × N
Illustrative flow — not a live capture.
Typical pattern Echo request flood
Engarde metric ICMP PPS, RTT
Layer L3 network
What to watch in Engarde
- RTT spikes or total loss under sustained echo traffic.
- Router/firewall ICMP policer behavior.
- Difference between edge IP vs. origin IP as target.
Running this simulation
Engarde ICMP simulation sends echo traffic to configured IPs. Pair with latency analysis reports for path visibility.
Mitigation perspective
ICMP rate limits and selective blocking are common; document what remains reachable for monitoring vs. attack surface.