News for hackers. Stuff that matters.
Re:TCP Connection Timeout Mystery by whirlwin on Monday March 25, 2024 @05:09PM (#39821298)
> Blocking ICMP can break of lot of things and offers no real benefits outside of a handful of specific edge cases.

Are you referring to local networks only?

It's very common to not allow ICMP by defaul to workloads in the cloud, e.g. in AWS.

Re:TCP Connection Timeout Mystery by fragmede on Monday March 25, 2024 @05:26PM (#39821435)
That's likely to be an implementation detail of how they've implemented TCP routing across a large fabric.
Re:TCP Connection Timeout Mystery by Hikikomori on Monday March 25, 2024 @06:31PM (#39821977)
AWS doesn't decide or even care about this, customers configure security group rules for their own services. Nothing is allowed by default, so if you want ICMP you would need to allow it, most font bother because it's not that helpful in a cloud environment (can just monitor the TCP port instead and get similar information).
Re:TCP Connection Timeout Mystery by immibis on Monday March 25, 2024 @06:43PM (#39822073)
This explains why some people have problems with IPv6 - if you block IPv6 Control Messages, then it will only work sometimes.
Re:TCP Connection Timeout Mystery by pajko on Wednesday March 27, 2024 @01:03PM (#39841700)
Fragmented packets won't work without ICMP.

Edit: here's a good page about the effects of disabling ICMP: https://www.rimscout.com/why-you-should-not-block-icmp/

Also there's some blackhole detection or how is it called.

However it's OK to block _parts_ of the ICMP protocol for security reasons, like echo and reply.