So I ran into this issue where doing
traceroute some-server.abc.com
returned ***
for multiple lines and finally reached maximum hops limit.
Doing a traceroute -T some-server.abc.com
works perfectly fine. I checked the man pages and by default traceroute
uses UDP protocol and -T forces it to use TCP probe packets.
What can be the possible reasons for such behaviour.
Also note that ping
works fine with this host.