Looks like it's just blocking non ICMP traceroute. You'll find lots of
sites that block that or ICMP as well.
try this:
$ sudo traceroute www.psbspeakers.com -I
traceroute to www.psbspeakers.com (174.120.194.72), 30 hops max, 60 byte
packets
1 derf.thecave.net (192.168.0.1) 0.132 ms 0.137 ms 0.147 ms
2 * * *
3 64.59.132.69 (64.59.132.69) 11.488 ms 11.685 ms 11.702 ms
4 rc2so-tge0-3-5-0.cg.shawcable.net (66.163.71.162) 13.636 ms 14.031
ms 14.033 ms
5 rd1ht-tge1-1-1.ok.shawcable.net (66.163.77.18) 31.177 ms 31.204
ms 31.212 ms
6 rc2wh-tge0-1-2-0-1.vc.shawcable.net (66.163.77.206) 48.446 ms
46.557 ms 46.526 ms
7 te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63) 47.682
ms 42.422 ms 46.888 ms
8 ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136) 71.327 ms
69.177 ms 68.829 ms
9 po31.dsr01.dllstx3.networklayer.com (173.192.18.225) 69.060 ms
67.565 ms 67.796 ms
10 po31.dsr01.dllstx2.networklayer.com (70.87.255.66) 79.755 ms 65.579
ms 65.570 ms
11 te5-1.car12.dllstx6.networklayer.com (70.87.254.226) 68.097 ms
76.906 ms 74.985 ms
12 48.c2.78ae.static.theplanet.com (174.120.194.72) 66.451 ms 67.059
ms 67.043 ms
You can also try www.tracert.com to try from different sources if you
suspect a routing issue with your ISP.
On 13-03-12 11:59 AM, Gustin Johnson wrote:
I would look at using mtr, it is usually much more accurate than plain
old traceroute. I would use mtr to track down latency or packet loss
issues (i.e. find the hop that is the problem).
Also it is important to note that that just because a traceroute or
ping fails, this does not mean that the service you are interested in
is also down. You really need to use a variety of tools to sort out
these kinds of issues (hping, "openssl s_client", and nmap are really
handy). These days with load balancers, content delivery networks,
and all sorts of security appliances, it can be really challenging to
know exactly what is going on.
Hth,
If you have control over both ends netcat (or the more modern ncat) is
really useful to verify connectivity.
On Tue, Mar 12, 2013 at 11:44 AM, Andrew Robinson
<[email protected] <mailto:[email protected]>> wrote:
Im thinking it may have something to do with shaw, as I'm on an
Allstream connection and am able to connect to the site and
complete the traceroute without issue.
For me the connection takes 10 hops to complete.
Sent from my Android phone using TouchDown (www.nitrodesk.com
<http://www.nitrodesk.com>)
-----Original Message-----
*From:* Greg King [[email protected] <mailto:[email protected]>]
*Received:* Tuesday, 12 Mar 2013, 11:28
*To:* CLUG General [[email protected] <mailto:[email protected]>]
*Subject:* Re: [clug-talk] Websites blocked?
I get exactly the same result with slightly different timing...
----- Original Message -----
From: "Hendrik Schaink" <[email protected]
<mailto:[email protected]>>
To: "CLUG General" <[email protected] <mailto:[email protected]>>
Sent: Tuesday, 12 March, 2013 11:17:58 AM
Subject: [clug-talk] Websites blocked?
Hello all,
In the past I used to be able to visit website www.psbspeakers.com
<http://www.psbspeakers.com> but
not lately. When performing a traceroute I never am arriving at my
destination point, appear to get blocked by some equipment
belonging to
"networklayer.com <http://networklayer.com>." Here is the
traceroute output:
hendrik@ivcadmin:~$ traceroute www.psbspeakers.com
<http://www.psbspeakers.com>
traceroute to www.psbspeakers.com <http://www.psbspeakers.com>
(174.120.194.72), 30 hops max, 60 byte
packets
1 router.infovisi.com <http://router.infovisi.com> (192.168.0.5)
0.526 ms 0.913 ms 0.904 ms
2 * * *
3 64.59.131.230 (64.59.131.230) 18.780 ms 18.813 ms 18.787 ms
4 rc2so-tge0-0-1-0.cg.shawcable.net
<http://rc2so-tge0-0-1-0.cg.shawcable.net> (66.163.77.9) 25.775
ms 25.779
ms 25.759 ms
5 rc1nr-pos0-7-4-0.wp.shawcable.net
<http://rc1nr-pos0-7-4-0.wp.shawcable.net> (66.163.76.194
<tel:%2866.163.76.194>) 37.729 ms 37.744
ms 37.719 ms
6 rc1wh-ge6-0-0-1.vc.shawcable.net
<http://rc1wh-ge6-0-0-1.vc.shawcable.net> (66.163.77.206
<tel:%2866.163.77.206>) 60.211 ms 59.246
ms 59.176 ms
7 te1-7.bbr01.eq01.chi01.networklayer.com
<http://te1-7.bbr01.eq01.chi01.networklayer.com> (206.223.119.63)
51.060 ms
43.073 ms 46.599 ms
8 ae20.bbr01.eq01.dal03.networklayer.com
<http://ae20.bbr01.eq01.dal03.networklayer.com> (173.192.18.136
<tel:%28173.192.18.136>) 74.186 ms
71.356 ms 67.249 ms
9 po31.dsr01.dllstx3.networklayer.com
<http://po31.dsr01.dllstx3.networklayer.com> (173.192.18.225
<tel:%28173.192.18.225>) 68.595 ms
po31.dsr02.dllstx3.networklayer.com
<http://po31.dsr02.dllstx3.networklayer.com> (173.192.18.227
<tel:%28173.192.18.227>) 66.877 ms 71.514 ms
10 po31.dsr01.dllstx2.networklayer.com
<http://po31.dsr01.dllstx2.networklayer.com> (70.87.255.66) 79.306 ms
po32.dsr02.dllstx2.networklayer.com
<http://po32.dsr02.dllstx2.networklayer.com> (70.87.255.70) 67.111 ms
po31.dsr01.dllstx2.networklayer.com
<http://po31.dsr01.dllstx2.networklayer.com> (70.87.255.66) 66.487 ms
11 te5-1.car12.dllstx6.networklayer.com
<http://te5-1.car12.dllstx6.networklayer.com> (70.87.254.226
<tel:%2870.87.254.226>) 82.970 ms
82.953 ms te6-1.car12.dllstx6.networklayer.com
<http://te6-1.car12.dllstx6.networklayer.com> (70.87.254.230
<tel:%2870.87.254.230>) 83.546 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Does any of you get anything better than this "feature?"
Hendrik schaink
_______________________________________________
clug-talk mailing list
[email protected] <mailto:[email protected]>
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected] <mailto:[email protected]>
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected] <mailto:[email protected]>
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
