isp - DynDNS configuration - second to last packet is timed out during tracert
2014-04
Zweihander
I have a NAS in a separate location which I connect into through a DynDNS domain I got for it. When I tracert to that DynDNS name, the following comes up:
1 3 ms 2 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms L***.CITY-VFTTP-***.verizon-gni.net [**.***.**.***]
3 5 ms 11 ms 11 ms G*-*-*-*.CITY-LCR-**.verizon-gni.net [***.***.***.***]
4 8 ms 5 ms 5 ms so-*-*-*-*.******-BB-****.verizon-gni.net [***.***.***.***]
5 22 ms 31 ms 23 ms P**-0-0.OTHERCITY-LCR-**.verizon-gni.net [***.***.***.***]
6 * * * Request timed out.
7 24 ms 21 ms 21 ms pool-***-**-***-***.othercity.fios.verizon.net [***.***.***.***]
As you can guess, the cities aren't far and the connection is all through Verizon fios. What I'm concerned about is the 6th line (which I haven't changed at all). Is that supposed to happen? Is there some way I can not have it time out and have a faster connection?
Thanks!
Paul
A tracert sends a packet that will expire at each point in the path to the destination. When a router receives a packet that has expired (TTL goes to zero) it should send an ICMP packet back to the source to let it know that the packet expired.
Tracert measures the time between the sending packet and the ICMP notification to work out the latency for each hop.
However, there is no guarantee that the ICMP packet will be sent. Firewalls are generally configured to silently drop any packet targetted at them, and many routers are configured to not send ICMP packets in this scenario.
The hop you are seeing no response from is configured in this way. It is perfectly normal and has no bearing on your connection speed. Tracert would indicate an issue if you had no responses beyond a certain point in the path. You are getting a 21ms response from the next hop after the one that doesn't respond, which is pretty good latency.
Alex Humphrey
I'm sadly spending my morning trying to get Take That tickets for my girlfriend. I did
tracert ticketmaster.co.uk
and got the following output
C:\Users\Alex>tracert ticketmaster.co.uk
Tracing route to ticketmaster.co.uk [209.104.32.143]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 26 ms 23 ms 23 ms 89.240.224.1
3 25 ms 25 ms 31 ms 62.24.254.216
4 26 ms 27 ms 26 ms 62.24.254.151
5 25 ms 24 ms 25 ms xe-11-0-0-rt001.man.as13285.net [78.151.225.3]
6 44 ms 36 ms 32 ms xe-11-1-0-rt001.sov.as13285.net [62.24.240.14]
7 32 ms 31 ms 31 ms xe-11-2-0-scr001.sov.as13285.net [78.144.1.130]
8 33 ms 30 ms 32 ms host-78-144-0-213.as13285.net [78.144.0.213]
9 33 ms 31 ms 31 ms ge-0-2-0-0.lonth-inter-2.interoute.net [195.66.2
26.53]
10 32 ms 34 ms 33 ms 209.104.32.34
11 33 ms 30 ms 31 ms 209.104.32.33
12 34 ms 33 ms 31 ms 209.104.32.34
13 49 ms 41 ms 31 ms 209.104.32.33
14 38 ms 36 ms 33 ms 209.104.32.34
15 44 ms 31 ms 32 ms 209.104.32.33
16 33 ms 33 ms 34 ms 209.104.32.34
17 32 ms 31 ms 33 ms 209.104.32.33
18 33 ms 33 ms 30 ms 209.104.32.34
19 32 ms 30 ms 32 ms 209.104.32.33
20 34 ms 33 ms 34 ms 209.104.32.34
21 32 ms 30 ms 32 ms 209.104.32.33
22 33 ms 43 ms 34 ms 209.104.32.34
23 86 ms 42 ms 99 ms 209.104.32.33
24 35 ms 31 ms 30 ms 209.104.32.34
25 59 ms 31 ms 32 ms 209.104.32.33
26 32 ms 32 ms 33 ms 209.104.32.34
27 34 ms 32 ms 31 ms 209.104.32.33
28 41 ms 32 ms 33 ms 209.104.32.34
29 33 ms 31 ms 31 ms 209.104.32.33
30 32 ms 32 ms 31 ms 209.104.32.34
Trace complete.
What does/could the hovering between those two IPs mean?
Ignacio Vazquez-Abrams
It means that the routing table on one of the routers in the loop is screwed up. Try a WHOIS on the addresses and talking to their technical contact; they may not know that it's broken.
joeqwerty
It's a routing loop. Those two routers each think that the other router has a route to the destination.
Senad Uka
It can mean that the router to which .33 needs to send data is down. It sometimes happen with my ISP.
Linker3000
BBC News reports that the site has crashed. Good luck