Tuesday, January 25, 2011

traceroute does not work, output is * * * but network is fine.

Hi, on my Linux box, traceroute does not work. the output is like this:

$ traceroute google.com

traceroute to google.com (209.85.231.104), 30 hops max, 52 byte packets
1  * * *
2  * * *
3  * * *
4  * * *

Can anyone tell me why its not working? any possible reasons behind it?

  • it could be that a firewall upstream from you is blocking the UDP packets Traceroute

    On modern Unix-like operating systems, the traceroute utility by default uses UDP datagrams with destination ports numbering from 33434 to 33534.

    radius : $ is more likely unix prompt rather than windows one and windows traceroute command is tracert. And the question tells about Linux...
    lalalalalalala : i realised this so i edited the answer.
    dbasnett : I thought trace route used ICMP packets. I did not know that unix based systems use UDP. Learn something new everyday.
  • This is probably because icmp TIME_EXCEEDED answer is filtered by the router/firewall that you use as default gateway or by your Linux system itself

    From radius
  • Try to use -T (tcp) or -U (udp) to bypass firewall.
    Some routers/firewall don't let icmp echo pass trough, that's why you'd use those 2 to by pass them.
    Anyway, contrary as stated in wikipedia, on my debian boxes traceroute still uses icmp packets and not udp.

    EDIT

    I was wrong...it uses udp...the icmp coming back are for an unreachable port...sorry

    From Pier

0 comments:

Post a Comment