On Wed, 2005-07-20 at 04:47 +0200, Anders Johansson wrote:
I don't really know what this tells me. It seems as though it works up to the 12th entry and dies?
Yeah, but it doesn't have to mean anything, since as I mentioned, not all sites respond to ICMP packets, and traceroute uses ICMP to do its thing
Actually, "traceroute" (at least on Unix/Linux machines) uses UDP packets to find out hops in between utilizing TTL. Not ICMP packets. http://www.private.org.il/mini-tcpip.faq.html#1.%20Of%20ping%20&% 20traceroute. Therefore, in my understanding, if there is a FW inbetween that doesn't allow any high port UDP packets (over port 33434 by default) to go though, or at least it wouldn't reply to the timed-out UDP packet to let the source to know its IP address, so you get.... 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * even in case the destination responses for pinging. Almost all of commercial web servers are protected by FWs. "traceroute" from a SuSe machine to any www.xxxxx.com may not work in many cases. Toshi