[Wylug-help] understanding traceroute output.

[Simon Wood]

Hi all.
I have a problem with my internet connectivity. There are a (not insignific=
ant) number of websites that I can't access. This has been the case since c=
hanging ISPs and their support department fails to find a solution claiming=
 it is beyond their control.

One site I can't 'see' is www.linuxtoday.com <http://www.linuxtoday.com>  -=
 so you can see the importance of this call for help :-)

I get (or something similar):

simon@columbo:~$ <mailto:simon@columbo:~$>  traceroute www.linuxtoday.com <=
http://www.linuxtoday.com>
traceroute to www.linuxtoday.com <http://www.linuxtoday.com>  (63.236.73.20=
), 30 hops max, 38 byte packets
 1  router (192.168.1.1)  20.348 ms  19.721 ms  18.466 ms
 2  pth-rb1.telehouse.core.plus.net (195.166.128.11)  25.361 ms  19.079 ms =
 19.915 ms
 3  212.159.1.3 (212.159.1.3)  22.266 ms  21.525 ms  21.813 ms
 4  pth-gw0.telehouse.core.plus.net (195.166.129.22)  21.881 ms  21.240 ms =
 21.963 ms
 5  lvl3gw.thn.packetexchange.net (212.187.197.193)  19.893 ms  21.280 ms  =
22.019 ms
 6  unknown.Level3.net (212.113.3.29)  21.752 ms  21.448 ms  21.888 ms
 7  so-7-0-0.mp2.London1.Level3.net (212.113.3.9)  22.193 ms  21.413 ms  19=
.801 ms
 8  so-1-0-0.mp2.NewYork1.Level3.net (212.187.128.153)  87.879 ms  87.289 m=
s  87.720 ms
 9  gigabitethernet5-1.core1.NewYork1.Level3.net (64.159.17.101)  89.630 ms=
  87.345 ms  85.840 ms
10  unknown.inet.qwest.net (209.244.160.130)  93.787 ms  93.201 ms  93.875 =
ms
11  jfk-core-02.inet.qwest.net (205.171.30.17)  91.736 ms  93.100 ms  93.66=
8 ms
12  ewr-core-01.inet.qwest.net (205.171.8.245)  91.905 ms  93.260 ms  91.83=
4 ms
13  ewr-cntr-01.inet.qwest.net (205.171.17.146)  91.940 ms  91.313 ms  91.9=
57 ms
14  msfc-22.ewr.qwest.net (63.146.100.34)  91.761 ms  91.233 ms  94.153 ms
15  * 63.236.93.180 (63.236.93.180)  92.787 ms !A *
16  63.236.93.180 (63.236.93.180)  91.749 ms !A * *
17  * * *
18  * 63.236.93.180 (63.236.93.180)  91.822 ms !A *
19  * * *
20  * 63.236.93.180 (63.236.93.180)  93.007 ms !A *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


A web-browser just times out getting the page. I know the site is up as I c=
an access it from my work account. My set up is small LAN with ADSL etherne=
t modem/firewall configured to run NAT.

So two questions:

1). Can anyone offer an idea of what might be wrong?

2). If it's not me (or something to do with my set up) how can I approach g=
etting it fixed?

Thanks,
Simon.