Re: [HELP] Traceroute
Alex Page [EMAIL PROTECTED] writes: On Thu, Apr 05, 2001 at 05:37:34PM +0100, Dominic Mitchell wrote: You probably want: TCP/IP Illustrated, Volume 1: The Protocols, Gah, I've got a copy of that on my shelf. Really should get round to reading it at some point... Ah, "bought any good books lately?". There are some books that are just good to _own_ -- Dave Hodgkinson, http://www.hodgkinson.org Editor-in-chief, The Highway Star http://www.deep-purple.com Interim CTO, web server farms, technical strategy
Re: [HELP] Traceroute
On Sat, Apr 07, 2001 at 06:59:44AM +0100, Dave Hodgkinson wrote: Alex Page [EMAIL PROTECTED] writes: TCP/IP Illustrated, Volume 1: The Protocols, Gah, I've got a copy of that on my shelf. Really should get round to reading it at some point... Ah, "bought any good books lately?". There are some books that are just good to _own_ I didn't buy it... it was a present from a guilty former employer when he didn't give me the permanent position he'd promised me when I joined the company after graduation. Also got O'Rielly's HTML and XHTML, which my girlfriend has since lost... *grr* Alex -- "I ask for so little. Just let me rule you, and you can have everything that you want." - Jareth, Labyrinth
Re: [HELP] Traceroute
On Thu, Apr 05, 2001 at 10:33:19AM -0400, Andy Williams wrote: Hi, Can any one tell me what this traceroute actually means... it has me completely confused (not that difficult actually!!) Yup. The machines on hops 11-24 aren't answering the traceroute packets, but are passing them on. Possibly a routeing loop if you'd normally expect to see fewer hops there. Roger (won't be along this evening, not getting paid for the last month's work. Gizza job!)
Re: [HELP] Traceroute
On Thu, Apr 05, 2001 at 10:33:19AM -0400, Andy Williams wrote: Hi, Can any one tell me what this traceroute actually means... it has me completely confused (not that difficult actually!!) traceroute 195.153.113.229 traceroute to 195.153.113.229 (195.153.113.229), 30 hops max, 40 byte packets 1 chromium.pair.net (209.68.1.224) 1.814 ms 1.067 ms 0.569 ms 2 beauty.pair.net (192.168.1.2) 1.744 ms 1.472 ms 0.813 ms 3 POS3-2.GW3.PIT1.ALTER.NET (157.130.48.161) 1.003 ms 1.520 ms 1.621 ms 4 518.at-2-0-0.XR1.DCA1.ALTER.NET (152.63.36.250) 6.362 ms 6.487 ms 6.001 ms 5 295.at-7-1-0.XR1.DCA8.ALTER.NET (146.188.163.10) 7.885 ms 6.676 ms 8.041 ms 6 POS6-0.BR2.DCA8.ALTER.NET (152.63.35.189) 8.887 ms 8.094 ms 8.770 ms 7 204.6.140.117 (204.6.140.117) 7.447 ms 8.928 ms 8.285 ms 8 ne.peering.tier1.us.psi.net (154.13.2.34) 14.977 ms 13.005 ms 12.713 ms 9 204.6.134.154 (204.6.134.154) 87.708 ms 87.232 ms 86.990 ms 10 5-11-leaf-int.lf1.cityreach.uk.psi.net (154.32.11.5) 83.906 ms 83.318 ms 83.721 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * Here it went th next router went wihtout responding for a while (it may have been rebooting). 25 ci217.cityreach.uk.psi.net (154.32.30.217) 97.396 ms !X * * 26 ci217.cityreach.uk.psi.net (154.32.30.217) 95.940 ms !X * 94.271 ms !X !X means the router administratively prohibited your packets from passing. ie: it disallows traceroutes. Try connecting to a service on that machine, eg: "telnet 195.153.113.229 80". That stands a better chance of working. Incidentally, the traceroute man page contains a couple of good examples of "funny" outputs. -Dom