6 ms·
One perspective: http://shouldiblockicmp.com/ http://shouldiblockicmp.com/ : - Don't block ICMP: Echo Request and Echo Reply, Fragmentation Needed (IPv4) / Pac
by westurner 3y ago
One perspective: http://shouldiblockicmp.com/ http://shouldiblockicmp.com/ :
- Don't block ICMP: Echo Request and Echo Reply, Fragmentation Needed (IPv4) / Packet Too Big (IPv6), Time Exceeded, and only within the boundary allow NDP and SLAAC (IPv6)
But presumably none of that helps solve for what traceroute is used to help diagnose.
"ICMP: The Good, the Bad, and the Ugly" (2016) https://blog.securityevaluators.com/icmp-the-good-the-bad-and-the-ugly-130413e56030 https://blog.securityevaluators.com/icmp-the-good-the-bad-an... ; blocking ICMP mitigates {Ping sweep, Ping flood, ICMP tunneling, Forged ICMP redirects,} but breaks {Path MTU discovery (PMTUD), TTL, ICMP Redirect}
ICMP > Redirect: https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol#Redirect https://en.wikipedia.org/wiki/Internet_Control_Message_Proto... ; Type 5
So this would drop just ICMP redirects:
sudo iptables -A OUTPUT -p icmp --icmp-type 5 -j REJECT
- toast0 3y agoWhat I block or don't for ICMP doesn't much matter when I'm tracerouting through networks I don't control,which is nearly all of them. Yeah, if I block the returns from my probes, I won't get useful results for traces to pretty much anywhere, but that should solve itself.