New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Traceroute
Look at hop 10 - why 2 IPs? 
Comments
Traceroute sends three ICMP echo packets for each hop. When you get two results like that for a single hop, it means that one of those packets went via a different route, for whatever reason. It could be load balancing or the main route was congested, or a number of other reasons.
its fine here http://pastebin.com/Jqd7Pdjh
@NickM IIRC the linux traceroute, unlike the Windows tracert, uses UDP instead of ICMP.
@Kuro It indeed does send UDP packets, and listens for ICMP Time Exceeded packets.
Im not too clued up on Windows crashology, but doesn't it also ping differently?
Talk about standards, a UNIX trace route can be done in seconds, where a Windows one takes minutes.
Yes - find this extremely irritating. I often start a trace route in Windows and then minimize and forget about it due to the amount of time it takes to complete.
Windows tracert sends ICMP packages because the answer to traceroutes (be it ICMP or UDP) is always ICMP, see: RFC 792.
Windows tracert is slower because it does not bomb out random UDP packages at a port all at once. If you want that use pathping which is available since Win XP.
I believe the reason for this is how Unix and Windows to the traceroutes. While Windows sends a packet with TTL 1, waits for it to return, then sends a packet with TTL 2, waits for it to return etc etc Unix just sends packets with TTL from 1-30 or so at the same time.