Tuesday, March 24, 2015

TTL expired in transit





pinging [192.x.x.xx] with 32 bytes of data:
Reply from 192.x.x.11: TTL expired in transit.
Reply from 192.x.x.11: TTL expired in transit.
Reply from 192.x.x.11: TTL expired in transit.
Reply from 192.x.x.11: TTL expired in transit.

Ping statistics for 192.x.x.xx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),


The TTL value determines the maximum amount of time an IP packet may live in the network without reaching its destination. It is effectively a bound on the number of routers an IP packet may pass through before being discarded. This message indicates that the TTL expired in transit.
Many routers will not answer ICMP, they will ignore ping requests..
TTL values do not always start at 255. Many hosts start at lower values. TTL does not count "seconds" but hop count. It decrements by 1 for each hop between hosts.
That wouldn't cause the issue we see where yours gets stuck in the private IP loop though



Conclusion of the problem
Increase the TTL value using the -i parameter with the ping command. For example see the below

 ping 192.168.XX.XX  -t -i 120


If the problem is still persist restart the client and destination client.
 

No comments:

Post a Comment