TTL expired in transit
I encountered a strange thing early this morning. The other party cannot remotely connect to the local host, both parties are ADSL to INTERNET, and the network status is normal. Use the PING command to test, the test results are 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, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The return represents TTL, expired in transit, represents TTL (life cycle) expired during transmission. What does it mean? Let me explain!
There are two reasons for this problem:
1) The TTL value is too small! The TTL value is less than the number of routers passing between you and the other host.
2) There are too many routers, and the number of routers passing through is greater than the TTL value!
Next, to find out the problem, you need to use the TRACERT command to view the routes passed by. The test results are 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.251
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, it can be clearly found that the route generation loop cannot be transferred between these four routes at 61.152.81.5, 61.152.81.6, 61.152.81.25, 61.152.81.26. Therefore, TTL expired in transit. Since we went out from 192.168.0.1 (gateway), to 192.168.0.251 (local route), to 61.129.99.217 (dedicated line gate), and finally went out 202.101.63.13-》61.152.81.14 (telecommunications route). Everything is relatively normal, indicating that the problem is not local, so it should be a telecommunications problem.
I called the telecommunications to report the repairs. The business staff didn't know what was going on. He didn't understand very well, so he had to say that he was calling a technical person. After a while, the telecommunications technician called to ask about the situation. The professionals were different. I knew what the problem was. I reported the IP to him and reported the routes on which routes were generated. He went to check it. The problem was solved later. Then I tested it with PING:
C:\ >ping
Pinging [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=40ms TTL=246
Ping statistics for 58.33.46.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 40ms, Average = 37ms
The problem is solved, but where is the problem? Afterwards, the telecom technician called again to explain. This is the problem. Since the new IP addresses starting with 58 have not been optimized, there may be a lot of routes passed by, and sometimes they may go abroad for a walk and come back. (Damn. This is the original quote from telecommunications technology)
There are two solutions to this problem now:
1. When you find that the IP starts at 58, re-dial, it is best to dial to 61, so there will be no problem.
2. Like telecom applications, change a port.
I encountered a strange thing early this morning. The other party cannot remotely connect to the local host, both parties are ADSL to INTERNET, and the network status is normal. Use the PING command to test, the test results are 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, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The return represents TTL, expired in transit, represents TTL (life cycle) expired during transmission. What does it mean? Let me explain!
There are two reasons for this problem:
1) The TTL value is too small! The TTL value is less than the number of routers passing between you and the other host.
2) There are too many routers, and the number of routers passing through is greater than the TTL value!
Next, to find out the problem, you need to use the TRACERT command to view the routes passed by. The test results are 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.251
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, it can be clearly found that the route generation loop cannot be transferred between these four routes at 61.152.81.5, 61.152.81.6, 61.152.81.25, 61.152.81.26. Therefore, TTL expired in transit. Since we went out from 192.168.0.1 (gateway), to 192.168.0.251 (local route), to 61.129.99.217 (dedicated line gate), and finally went out 202.101.63.13-》61.152.81.14 (telecommunications route). Everything is relatively normal, indicating that the problem is not local, so it should be a telecommunications problem.
I called the telecommunications to report the repairs. The business staff didn't know what was going on. He didn't understand very well, so he had to say that he was calling a technical person. After a while, the telecommunications technician called to ask about the situation. The professionals were different. I knew what the problem was. I reported the IP to him and reported the routes on which routes were generated. He went to check it. The problem was solved later. Then I tested it with PING:
C:\ >ping
Pinging [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=40ms TTL=246
Ping statistics for 58.33.46.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 40ms, Average = 37ms
The problem is solved, but where is the problem? Afterwards, the telecom technician called again to explain. This is the problem. Since the new IP addresses starting with 58 have not been optimized, there may be a lot of routes passed by, and sometimes they may go abroad for a walk and come back. (Damn. This is the original quote from telecommunications technology)
There are two solutions to this problem now:
1. When you find that the IP starts at 58, re-dial, it is best to dial to 61, so there will be no problem.
2. Like telecom applications, change a port.