7

this is the result of my traceroute

    traceroute   www.google.com
traceroute to www.google.com (216.58.211.228), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.061 ms  1.709 ms  2.262 ms
 2  * * *
 3  10.103.5.41 (10.103.5.41)  41.594 ms  43.136 ms  44.617 ms
 4  172.29.24.33 (172.29.24.33)  50.849 ms  51.574 ms  52.316 ms

What does having * * * mean in the command traceroute? and How can you cope with that situation?

Karim Michel
  • 75
  • 2
  • 6
  • 1
    Cope with what situation? What is it that you think is happening on this route? – joeqwerty Oct 31 '15 at 18:29
  • I'd be more concerned about those routers on the path which did respond. All of them have RFC1918 addresses. That makes me wonder how many layers of NAT the connection goes through. – kasperd Oct 31 '15 at 21:13

2 Answers2

5

It means that the affected host (in your example, the second one) did not reply to the traceroute. As by default traceroute uses an UDP port, you can change the discovery protocol to use ICMP/PING using the "-I" option. Apart that, you can not do anything more.

shodanshok
  • 44,038
  • 6
  • 98
  • 162
5

It means that a packet with a tweaked TTL did not return an appropriate ICMP TTL exceeded packet, or that those packets were lost on the way back, within the given period traceroute waits for them. This CAN mean, that the host on the way is not generating them properly, if at all.

There is little you can do about this. You can change the protocol traceroute uses for its discovery (as described by shodanshok), or increase the timeout (traceroute -w 15 for example). Also try to reduce the number of requests sent (-N 5).

P.S. You can also try to use some tool to utilise RECORD_ROUTE for example hping3. But I cannot give you any more details as I have never been able to use it.

Konrad Gajewski
  • 1,498
  • 3
  • 15
  • 29