networking - trace route vs ping time differences -
when pinging ip address average time 71.1 ms
when using tracert same ip shows higher times (around 70 ms each node..), can explain differences?
c:\users\user648026>ping 152.36.54.101 pinging 152.36.54.101 32 bytes of data: reply 152.36.54.101: bytes=32 time=89ms ttl=60 reply 152.36.54.101: bytes=32 time=64ms ttl=60 reply 152.36.54.101: bytes=32 time=71ms ttl=60 reply 152.36.54.101: bytes=32 time=63ms ttl=60 c:\users\user648026>tracert 152.36.54.101 tracing route host-123 [152.36.54.101] on maximum of 30 hops: 1 69 ms 65 ms 70 ms someipwashere 2 94 ms 71 ms 65 ms someipwashere 3 148 ms 73 ms 64 ms someipwashere 4 72 ms 66 ms 66 ms someipwashere 5 64 ms 73 ms 65 ms host [152.36.54.101] trace complete. c:\users\user648026>tracert 152.36.54.101 tracing route host-123[152.36.54.101] on maximum of 30 hops: 1 70 ms 78 ms 63 ms someipwashere 2 68 ms 104 ms 101 ms someipwashere 3 69 ms 117 ms 65 ms someipwashere 4 72 ms 69 ms 71 ms someipwashere 5 65 ms 64 ms 65 ms host [152.36.54.101]
i think misunderstand output traceroute. each line represents hop, , there 3 attempts each hop (the 3 columns). intermediate hops can have high times because generating icmp error messages low priority router, , when has time, priority routing packets.
the last line in have entire path source destination, , 3 times comparable ping times.
Comments
Post a Comment