3 ms·
You are right. My comment can't solve the whole story. Still, some middlebox/stateful firewall/etc. messing with 169.0.0.0/8 is plausible.
by Existing4190 3y ago
You are right. My comment can't solve the whole story.
Still, some middlebox/stateful firewall/etc. messing with 169.0.0.0/8 is plausible.
- xnyan 3y agoActually I think you might still be right. Ping uses ICMP, which is almost never blocked in my experience. I learned that because early in my career I too assumed a successful ping = TCP and UDP also work.
- deleted 3y ago[deleted]
- rstuart4133 3y agoSimilar happened to me not so long ago. One day a junior admin asked me to diagnose who ssh to a box started hanging. After a bit of diagnosis it became evident TCP's 3 way handshake got through, and then it all stopped. No normal network behaves like this. My answer was "some network admin is having fun with a middleware box", you will have to speak with them. They did, and the response that came back is "we are moving to a network with real security". Access was restored. It was a Palo Alto NGFW as others have mentioned. IMHO the industry looking for way to move high priced gear, and they convince someone with a sparrow problem with barely knows how to handle an air rifle to buy bazooka's. A bit of collateral damage is to be expected....
- js2 3y agoFiltering + established connection tracking: https://news.ycombinator.com/item?id=39822214 https://news.ycombinator.com/item?id=39822214