Подскажите, что значит такая вот странность
Веб-сервер недоступен уже больше суток вместе с любыми контактами хостера, так что вынужден спросить здесь. При попытке пингануть сервер вылезает следующее: Pinging 84.19.183.64 with 32 bytes of data: Reply from 193.22.254.200: TTL expired in transit. Reply from 193.22.254.200: TTL expired in transit. Reply from 193.22.254.200: TTL expired in transit. Reply from 193.22.254.200: TTL expired in transit. Ping statistics for 84.19.183.64: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms А при трассировке и вовсе бред какой-то — до KeyWeb-овского датацентра все прекрасно проходит, но за один хоп до сервера трассировка зацикливается: 11 67 ms 69 ms 69 ms LEI-3-pos220.de.lambdanet.net [217.71.96.62] 12 77 ms 79 ms 76 ms KW-ERF3.de.lambdanet.net [217.71.107.118] 13 69 ms 72 ms 70 ms rdsmaster226.keyvirtual.de [84.19.186.57] 14 68 ms 69 ms 71 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] 15 67 ms 68 ms 71 ms rdsmaster226.keyvirtual.de [84.19.186.57] 16 74 ms 73 ms 75 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] 17 71 ms 70 ms 68 ms rdsmaster226.keyvirtual.de [84.19.186.57] 18 72 ms 73 ms 71 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] 19 69 ms 74 ms 66 ms rdsmaster226.keyvirtual.de [84.19.186.57] 20 78 ms 82 ms 74 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] 21 78 ms 76 ms 76 ms rdsmaster226.keyvirtual.de [84.19.186.57] 22 84 ms 84 ms 82 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] 23 72 ms 76 ms * rdsmaster226.keyvirtual.de [84.19.186.57] 24 70 ms 81 ms 69 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] О чем могут говорить данные симптомы?
На сайте с 15.01.2006
19 декабря 2006, 17:53
14 68 ms 69 ms 71 ms vl1.c6500.ef.de.megabit.biz [193.22.254.200] 15 67 ms 68 ms 71 ms rdsmaster226.keyvirtual.de [84.19.186.57] Маршруты зациклены друг на друга. потому и ТТЛ экспайред.
Изучаем правила форума ( )
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 2 2 ms 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]
Подскажите что это за глюк и как это исправить?
TTL Expired in Transit — Reason and Solution
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
- Infinite loop due to the incorrect routing table entries
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.
-
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.
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.
The first step is to perform a tracert test and check the actual location of the error.
Open the command prompt on your Windows computer. Type tracert www.corenetworkz.com and press the enter button.
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.
Make sure the Time To Live value set for the packet is reasonable.
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.
C:\Windows\system32>ping google.com -i 3
Pinging google.com [2404:6800:4007:804::200e] with 32 bytes of data:
Reply from 2404:6800:4007:804::200e: TTL expired in transit.
Reply from 2404:6800:4007:804::200e: TTL expired in transit.
Reply from 2404:6800:4007:804::200e: TTL expired in transit.
Reply from 2404:6800:4007:804::200e: TTL expired in transit.
Ping statistics for 2404:6800:4007:804::200e:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
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.
Alex George is a Computer Science and Engineering graduate. He completed networking courses CCNA, CCNP, and MSCE. Now, he works as a Senior Network Engineer in a leading MNC. Webmaster Skills: Alex has been a blogger since 2004. He has a working knowledge of HTML, CSS, PHP, and JavaScript.
- Get link
- Other Apps
What does «TTL expired in transit» mean on a ping attempt?
We get the message “TTL expired in transit” when we try to ping to a server in a different network segment. When we run tracert, 4 ip addresses repeat themselves indefinitely:
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 . What are the basic steps for troubleshooting this error?
7,380 3 3 gold badges 30 30 silver badges 43 43 bronze badges
asked Jul 13, 2009 at 5:23
705 1 1 gold badge 5 5 silver badges 8 8 bronze badges
8 Answers 8
As stated in all answers above there is loop in routing that is causing TTL to expire.
Check route on the devices whose IP addresses are repeating. On Linux you can use
route -n as root user to see current routing table. On windows you can go to cmd and use command
route print to see current routing table. On cisco manageable switches you can use command
show ip route Using above commands on all the four IPs that are repeating you should see which routing table is wrong. One of the four devices / hosts involved should ideally route traffic to destination you are pinging using some other gateway.
answered Jul 13, 2009 at 8:42
Saurabh Barjatiya Saurabh Barjatiya
4,703 2 2 gold badges 30 30 silver badges 34 34 bronze badges
You’ve got a circular route in your networking configurations, check your routing tables on the involved devices.
«TTL expired in transit» is related to the TTL value of the packet; every router it passes through lowers it by one. If it hits 0, the packet is dropped and an ICMP message (the ‘expired in transit’ message) is sent to the sender. It prevents infinite loops, where packets travel in circles forever.
5 3 3 bronze badges
answered Jul 13, 2009 at 5:26
593 3 3 silver badges 8 8 bronze badges
It’s not truly exact, the packet is not return to the sender but only an icmp message.
Jul 13, 2009 at 6:15
While the packet itself is not returned and an ICMP message (this TTL expired message) is sent back to the source, the point about the route-loop and TTL decrement explanation is correct.
Jul 13, 2009 at 6:49
IP packet has a TTL flag. This one is decreased by 1 each time the packet is routed. When the value become 0 the router drop the packet and send an ICMP message Time-to-live exceeded in transit.
This is done to prevent packets to be routed infinitely when there is routing problem on networks. This is your case here, you have a routing loop so that the packet never reach is destination and is finally dropped by one of the router because the TTL reach 0.
answered Jul 13, 2009 at 5:29
9,643 26 26 silver badges 46 46 bronze badges
While checking the routing tables of the four routers, focus on the network mask of the routes and if the router ist able to route » classless «.
On older Ciscos you need to explicitly enable this, otherwise they will route whole classful networks instead of your subnets. E.g. configuring 10.20.30.0/24 will result in a route like 10.0.0.0/8 .
answered Jul 13, 2009 at 8:02
2,875 18 18 silver badges 14 14 bronze badges
You make no mention of protocol, but I find that the overuse of static routes leads to the error quite often. Using a dynamic routing protocol should solve this with little effort from the administrators.
I would simply say to start at layer-1. Makes sure the router is on, and that the port linking it to the network is up up. Then map your route from your ICMP source to the destination router, examining the routing table at each hop along the path.
answered Jul 13, 2009 at 9:42
HeavyObjectLifter HeavyObjectLifter
131 1 1 gold badge 3 3 silver badges 10 10 bronze badges
When pinging resulted in Expired In Transit. short diagram — ISP ==> Router ==> Switch ==> to PCs
If ISP can see their device then you may need to reboot the swich. If it works then you are all set. If not, then you may need to reboot the router.
I got the same error message. I rebooted the switch and everything came back up.
answered Sep 2, 2009 at 20:53
Lake Seri Lake Seri
OK, so I’ll chime in with everyone else. You have a routing loop as evidenced by the fact that the ICMP Echo Request keeps looping between the same 4 routers. Check the routing tables on the routers, starting with the router at x.x.x.250.
answered Sep 2, 2009 at 20:58
110k 6 6 gold badges 81 81 silver badges 172 172 bronze badges
I received a TTL expired in transit message and the problem was an erroneous entry in DHCP.
Someone had added the same host name in the DHCP server with a static IP address(10.x.x.11), while the host had also leased a new dynamic IP address (10.x.x.22).
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),