Lion Cipher Lab

Diagnose a path MTU black hole with ping and tracepath — then fix it without opening ICMP wide

Why it matters

One of the most common 'hardening' tips you will ever be given is 'block ICMP, it is only ping'. It is wrong in a way that is hard to see: ICMP also carries the message that tells a sender 'that packet is too big for the next link, make it smaller'. Block that and you get a black hole — websites that load their first few lines and then freeze, file transfers and VPNs that connect and then hang, SSH that logs in and then stalls on a big command output — while ping-sized tests look fine. Help desks lose days to it. In this lab you build the broken network yourself, measure exactly how it fails,…

What you'll learn

Steps in this lab

  1. The idea in plain language: MTU, the DF bit, and the message nobody should block
  2. Start a throwaway privileged container and install the tools
  3. Why four namespaces, not three — the narrow link has to be in the middle
  4. Build the network: four namespaces, three virtual cables, two routers
  5. Measure the path MTU by hand with ping -M do
  6. Binary-search the path MTU, then let tracepath confirm it
  7. Start a web server and a measuring helper (the healthy baseline)
  8. Create the black hole: the 'block all ICMP' hardening rule
  9. Fix A (the proper fix): let fragmentation-needed through, and nothing else
  10. Fix B (the workaround): TCP MSS clamping — and measure it
  11. The negative you must see: MSS clamping does nothing for UDP
  12. When to reach for which fix — and why PLPMTUD exists
  13. Honest limits of this lab

Open the full interactive lab →