hub vs. router

scowles · 11-08-2004, 07:53 AM

The traceroute man pages have a good description of "how" traceroute works, but if you don't understand
ICMP, then it probably won't make much sense. Also, while reading the man page, take note of the "-I" command line switch. The windows version of traceroute (tracert) uses this switch.

BTW: There is also a rather dated, but cool program called tcptraceroute

TreeHugger · 11-08-2004, 10:33 AM

this is a cool thread. What happens then when I get this:

Code:

 1  arnor (192.168.1.254)  0.242 ms  0.117 ms  0.104 ms
 2  192.168.1.1 (192.168.1.1)  94.484 ms  0.594 ms  0.561 ms
 3  217.47.202.58 (217.47.202.58)  10.513 ms  11.737 ms  11.779 ms
 4  217.47.70.161 (217.47.70.161)  10.215 ms  13.308 ms  13.974 ms
 5  217.41.168.13 (217.41.168.13)  11.045 ms  12.262 ms  13.465 ms
 6  217.41.168.65 (217.41.168.65)  11.057 ms  17.123 ms  12.744 ms
 7  217.41.168.114 (217.41.168.114)  11.199 ms  12.159 ms  17.548 ms
 8  217.41.168.42 (217.41.168.42)  11.837 ms  11.808 ms  10.725 ms
 9  217.47.202.114 (217.47.202.114)  10.545 ms  10.104 ms  11.440 ms
10  core1-pos11-1.ealing.ukcore.bt.net (194.72.17.113)  11.026 ms  10.477 ms  12.257 ms
11  194.74.65.202 (194.74.65.202)  12.031 ms  13.241 ms  9.887 ms
12  linx.gw-backbone-a.lon.schlund.net (195.66.224.98)  11.234 ms  11.290 ms  12.259 ms
13  so-7000.gw-backbone-a.bs.ka.schlund.net (212.227.120.0)  101.539 ms  24.202 ms  25.469 ms
14  a0kac1a.gw-dists-a.bs.ka.schlund.net (212.227.116.208)  177.284 ms  86.813 ms  24.921 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

is this some sort of firewall or DHCP problem?

the man page says

Quote:

If there is no response within a 5 sec. timeout interval (changed with the -w flag), a "*" is printed for that probe.

but why would that be?