Ttl expired in transit как исправить

Столкнулся вот с такой проблемой.

Pinging yahoo.com with 32 bytes of data:

Reply from 10.2.131.38: TTL expired in transit.
Reply from 10.2.131.34: TTL expired in transit.
Reply from 10.2.131.38: TTL expired in transit.
Reply from 10.2.131.38: TTL expired in transit.

Ping statistics for yahoo.com:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 0ms, Maximum = 0ms, Average = 0ms

Команда tracert показывает следующие.

Tracing route to yahoo.com over a maximum of 30 hops

 1    <1 ms    <1 ms    <1 ms  [10.2.128.81]
 2     2 ms    <1 ms     1 ms  [10.2.130.10]
 3     1 ms     2 ms     1 ms  [10.2.131.33]
 4     3 ms     1 ms     2 ms  [10.2.131.38]
 5     3 ms     3 ms     3 ms  [10.2.131.33]
 6     2 ms     3 ms     2 ms  [10.2.131.38]
 7     4 ms     3 ms     5 ms  [10.2.131.33]
 8     4 ms     3 ms     5 ms  [10.2.131.38]
 9     4 ms     6 ms     5 ms  [10.2.131.33]
10     5 ms   208 ms   114 ms  [10.2.131.34]
11    10 ms     3 ms     8 ms  [10.2.131.33]
12   229 ms    11 ms   268 ms  [10.2.131.38]
13     7 ms     7 ms     5 ms  [10.2.131.37]
14   244 ms   259 ms     8 ms  [10.2.131.38]
15     7 ms     5 ms     6 ms  [10.2.131.33]
16     7 ms    10 ms     7 ms  [10.2.131.38]
17     9 ms     7 ms     7 ms  [10.2.131.33]
18     7 ms     8 ms     7 ms  [10.2.131.34]
19    12 ms     9 ms    10 ms  [10.2.131.37]
20     9 ms     9 ms     9 ms  [10.2.131.38]
21    13 ms     9 ms    10 ms  [10.2.131.33]
22    10 ms     9 ms     9 ms  [10.2.131.38]
23    12 ms    12 ms     8 ms  [10.2.131.33]
24    10 ms    12 ms    11 ms  [10.2.131.38]
25    10 ms    12 ms    12 ms  [10.2.131.33]
26    12 ms    12 ms    14 ms  [10.2.131.38]
27    11 ms    15 ms    12 ms  [10.2.131.37]
28    14 ms    13 ms    13 ms  [10.2.131.34]
29    14 ms    16 ms    13 ms  [10.2.131.33]
30    15 ms    15 ms    14 ms  [10.2.131.38]

Trace complete.

Подскажите что это за глюк и как это исправить?

TTL Expired in Transit is one of the common ping error messages you may receive in network troubleshooting. This tutorial explains the meaning of this error message TTL Expired in Transit and how to solve it.

Let us check the meaning of this error message first.

Meaning of TTL Expired in Transit

In simple words, TTL Expired in Transit tells the Time To Live value set for the ping packets is too low while traveling through the network before reaching the destination.

To understand it, we need to know the variable TTL.

TTL =Time To Live

In other words, the TTL value decides the life span of a packet.

The TTL value set on a packet will reduce by one when that packet passes through each hop in the network.

In a computer network, the term hop refers to a router.

For example, if the Time To Live value set on a packet is 3, it will pass through 3 hops. At the third hope, the TTL value reduces to become zero.

So, what happens when TTL expires? The packet will not travel to the next hop.

If a router sees the TTL value as zero, it will drop the packet.

This procedure helps to avoid the infinite looping of packets. It is the primary use of the TTL variable. However, if the TTL value becomes zero before reaching the destination, it will result in this error.

Let us check the reasons for receiving the ping reply TTL Expired in Transit.

Possible Reasons for TTL Expired in Transit

1. Infinite loop due to the incorrect routing table entries
2. TTL Value of a packet is set very low.

Finding the exact reason behind this error is a must to fix it. The step-by-step solution provided below in this article will help you solve this issue.

How to Solve TTL Expired in Transit?

The first solution will clear the current routing tables on your network devices and get a fresh routing table. If it does not work, you need to edit the routing table entries based on the Tracert test result.

1. Power Cycle the Local Network
   • Disconnect your PC/Laptop from the network. If your device is using WiFi, disconnect it. If it is a wired connection, disconnect the Ethernet/USB cable.
   • Restart your computer/laptop.
   • Power off the router.
   • Power off the modem and wait for two minutes.
   • Power on the modem and wait for the Power and Network lights to steady.
   • Power on the router and wait for the Power and Network lights to steady.
   • Reconnect your device (SmartPhone/Laptop/PC) to the network.

   Now ping the destination address again and check whether the issue persists. If the ping fetches the same error, you should follow the steps below.

2. Use the Tracert to Check the actual location of the error.

   The first step is to perform a tracert test and check the actual location of the error.

   • On Windows Platform

     Open the command prompt on your Windows computer. Type tracert www.corenetworkz.com and press the enter button.

     

   • On Linux Platform

     Open the Linux terminal and type traceroute www.corenetworkz.com, and press enter key.

   If you are not sure about the working of this command, you may visit the link below.

3. Check the Routing Table for an infinite loop.

   In most scenarios, the reason behind receiving the TTL Expired in Transit is a misconfigured router and a routing loop.

   We need to correct the router configuration and make sure that there is no routing loop.

   We can check the routing table on a computer by using the command prompt command provided below.

   route print

   

   This command will show the routing table stored on your PC.

   If you receive TTL Expired in Transit error on Cisco devices, you need to use a different command to fix it.

   The command to display the routing table in the Cisco router is:

   show ip route

   If you have Juniper devices on your network, use the show route table command.

   You need to delete the wrong entry in the routing table to resolve TTL Expired in Transit error.

   To delete a wrong entry on the routing table, use the route delete command.

4. Increase the Time To Live value of a packet.

   Make sure the Time To Live value set for the packet is reasonable.

   You can increase the TTL value of a packet by using the ping parameter -i.

Let me explain how to change the TTL value of a ping packet with an example. Have a look at the command below.

ping corenetworkz.com -i 3

You can see the reply on the Command Prompt when I set the TTL value 3.

You can see how the reply changed when I changed the TTL value from 3 to 30.

Let me show you the result when I ping the Google with modified TTL value.

I hope this tutorial helped you to identify and rectify the ping reply TTL Expired in Transit error. Allow me to introduce other similar ICMP error messages.

1. Destination Host Unreachable
2. Destination Net Unreachable
3. Request Timed Out
4. Error 678: The Remote Computer Did Not Respond

Что означает «истек срок действия при передаче» при попытке пинга?

14    60 ms    59 ms    60 ms  xxx.xxx.xxx.2
15    83 ms    81 ms    82 ms  xxx.xxx.xxx.128
16    75 ms    80 ms    81 ms  xxx.xxx.xxx.249
17    81 ms    78 ms    80 ms  xxx.xxx.xxx.250
18    82 ms    80 ms    77 ms  xxx.xxx.xxx.2
19   102 ms   101 ms   100 ms  xxx.xxx.xxx.128
20   101 ms   100 ms    98 ms  xxx.xxx.xxx.249
21    97 ms    98 ms    99 ms  xxx.xxx.xxx.250
...

Ответы:

route -n 

route print

show ip route

Pinging host.example.com [10.x.x.22] with 32 bytes of data:
Reply from 10.x.x.11: TTL expired in transit.
Reply from 10.x.x.11: TTL expired in transit.
Reply from 10.x.x.11: TTL expired in transit.
Reply from 10.x.x.11: TTL expired in transit.

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