This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

time-to-live exceeded

0

Team The trace below is displaying time-to-live exceeded what does that indicate, When I see the error, the page fails, but when this does not occur, you do not see and error on the webpage I have no idea what the time-to-live means how does this occur on the internet Help please thanks

https://www.cloudshark.org/captures/2ec18fc1305a

asked 20 Mar '14, 21:12

ejohnson7's gravatar image

ejohnson7
119912
accept rate: 0%


One Answer:

2

It means your IP packets (the ones carrying your web HTTP traffic, which is over TCP), have crossed too many router hops. Each router will decrement the TTL field in your sent IP packets, and when it reaches 0 the last router will drop the IP packet and respond with an ICMP packet with a TTL exceeded error code.

This usually happens if there's a loop in the router topology somewhere between you and the web server, either due to a misconfiguration, or a micro-loop due to a router reconvergence event. The latter don't usually last long (a few minutes at most), while the former can last a long time until someone fixes it.

To see where it's getting looped, do a traceroute to the web server's IP address you're trying to reach (in your example, 195.35.91.71). It appears to be somewhere in London, off of Level-3's network, named worldpay.com maybe? It's not exceeding TTL for me, so it's probably a local issue near you.

answered 20 Mar '14, 21:51

Hadriel's gravatar image

Hadriel
2.7k2939
accept rate: 18%

2

The TTL exceeded would usually come from a different IP, than the target system. So, in this case something is faking those frames, maybe a firewall or a QoS device. Especially the delta time between the first SYN and the TTL exceeded, makes me believe it's the local firewall of the OP.

(20 Mar '14, 23:23) Kurt Knochner ♦
2

The ICMP's TTL is 251 when it arrives at your host so I'd say the router detecting the loop is 4 hops away. The RESET packet from the same (webserver's) IP address arrives with a TTL of 255 so your adjacent Cisco router obviously does NAT/FW for you.

(21 Mar '14, 00:30) mrEEde
1

I also found it interesting that the TARGET was replying with the TTL ICMP and not the intermediate router.

(21 Mar '14, 10:14) Rooster_50

thanks much for the help

(22 Mar '14, 21:08) ejohnson7

Hint: If a supplied answer resolves your question can you please "accept" it by clicking the checkmark icon next to it. This highlights good answers for the benefit of subsequent users with the same or similar questions.

(24 Mar '14, 09:01) Kurt Knochner ♦