tracert (or traceroute, depending on the system you're using) is a variant on ping. Rather than just echoing whether the destination host is reached, the ICMP (Internet Control Message Protocol) packet instructs each device it passes through to echo back its name and the status of the request.
And yeah, it's dependent on the source of the trace. If Cheryl tried to do a trace from London, it would give her the working path from London. This isn't necessarily a bad thing to capture. It's a good base for comparison.
The important thing is the trace from her connection in Somerset, which will show where the route breaks. It's also worth doing a trace to a server at Pair that's reachable from Somerset; comparing the three routes (London, working-at-home and not-working-at-home) will give a pretty clear indication which router is fried.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2006-02-08 12:41 am (UTC)tracert(ortraceroute, depending on the system you're using) is a variant onping. Rather than just echoing whether the destination host is reached, the ICMP (Internet Control Message Protocol) packet instructs each device it passes through to echo back its name and the status of the request.And yeah, it's dependent on the source of the trace. If Cheryl tried to do a trace from London, it would give her the working path from London. This isn't necessarily a bad thing to capture. It's a good base for comparison.
The important thing is the trace from her connection in Somerset, which will show where the route breaks. It's also worth doing a trace to a server at Pair that's reachable from Somerset; comparing the three routes (London, working-at-home and not-working-at-home) will give a pretty clear indication which router is fried.