TTL expired in transit
This morning, something strange happened. The other party cannot remotely connect to the local host. Both parties connect to the Internet through ADSL, and the network status is normal. Run the ping command. The test result is as follows:
C: \ Ping 58.33.46.92
Pinging [58.33.46.92] with 32 bytes of data:
Reply from 61.152.81.25: TTL expired in transit.
Ping statistics for 58.33.46.92:
Packets: Sent = 4, stored ED = 4, lost = 0 (0% loss ),
Approximate round trip times in Milli-seconds:
Minimum = 0 ms, maximum = 0 ms, average = 0 ms
The return value indicates that TTL expired in transit indicates that TTL expires during transmission. What does this mean? Let me explain it!
There are two reasons for this problem:
1) the TTL value is too small! The TTL value is less than the number of routers that pass through the host.
2) There are too many routers. The number of routers passing through is greater than the TTL value!
To locate the problem, run the tracert command to view the route. The test result is as follows:
C: \> tracert-D 58.33.46.92
Tracing Route to [58.33.46.92]
Over a maximum of 30 hops:
1 6 MS 5 MS 5 MS 192.168.0.1
2 10 MS 6 MS 5 MS 192.168.0.20.
3 245 MS 131 MS 146 MS 61.129.99.217
4 18 MS 19 MS 20 MS 202.101.63.13
5 20 MS 16 MS 18 MS 61.152.81.14
6 22 MS 17 MS 19 MS 61.152.81.5
7 16 MS 14 MS 20 MS 61.152.81.6
8 21 MS 15 MS 19 MS 61.152.81.25
9 20 MS 16 MS 18 MS 61.152.81.26
10 20 MS 19 MS 15 MS 61.152.81.5
11 15 MS 14 MS 19 MS 61.152.81.6
12 20 MS 19 MS 15 MS 61.152.81.25
13 17 MS 19 MS 19 MS 61.152.81.26
14 17 MS 19 MS 15 MS 61.152.81.5
15 18 MS 18 MS 20 MS 61.152.81.6
16 17 MS 18 MS 15 MS 61.152.81.25
17 17 MS 19 MS 19 MS 61.152.81.26
18 16 MS 19 MS 14 MS 61.152.81.5
19 16 MS 19 MS 14 MS 61.152.81.6
20 17 MS 19 MS 14 MS 61.152.81.25
21 16 MS 20 MS 19 MS 61.152.81.26
22 16 MS 19 MS 20 MS 61.152.81.5
23 16 MS 20 MS 19 MS 61.152.81.6
24 17 MS 19 MS 19 MS 61.152.81.25
25 17 MS 18 MS 20 MS 61.152.81.26
26 17 MS 20 MS 19 MS 61.152.81.5
27 18 MS 17 MS 24 MS 61.152.81.6
28 18 MS 20 MS 19 MS 61.152.81.25
29 19 MS 19 MS 20 MS 61.152.81.26
30 19 MS 20 MS 18 MS 61.152.81.5
Trace complete.
Through monitoring, we can clearly find that routes generate loops at 61.152.81.5, 61.152.81.6, 61.152.81.25, 61.152.81.26, and the four routes cannot be transferred between them. Therefore, TTL expired in transit is caused. Since everything goes out from 192.168.0.1 (GATEWAY) to 192.168.0.20.( local route), then to 61.129.99.217 (leased line), and then 202.101.63.13-61.152.81.14 (Telecom route) is normal, it indicates that the problem is not local, so it should be a telecom problem.
After calling Telecom for repair, the business staff did not know what was going on, and he did not understand it. He had to call a technology, after a while, the technical staff of China Telecom called to ask the situation. The experts were very different and they knew what the problem was. I reported the IP address to him, after reporting the route generation loops, he checked the routes and solved the problem later. Then, Ping them to test the problem:
C: \> Ping yurenliang.vicp.net
Pinging yurenliang.vicp.net [58.33.46.92] with 32 bytes of data:
Reply from 58.33.46.92: bytes = 32 time = 37ms TTL = 246
Reply from 58.33.46.92: bytes = 32 time = 40 ms TTL = 246
Ping statistics for 58.33.46.92:
Packets: Sent = 4, stored ED = 4, lost = 0 (0% loss ),
Approximate round trip times in Milli-seconds:
Minimum = 35 ms, maximum = 40 ms, average = 37 Ms
The problem is solved, but where is the problem? Afterwards, the telecom technical staff called again to explain the problem. This is the problem. Because the new IP addresses starting with 58 are not optimized, there may be a large number of routes, and sometimes they may go abroad for a round and come back. (Dizzy. This is the original reference of China Telecom technology)
There are two solutions to this problem:
1. When the IP address is found to start with 58, it is best to dial it again.
2. Change a port like a telecom application.