Diagnose co-location networking problem

Bill Vermillion bv at wjv.com
Thu Dec 28 13:46:46 PST 2006


Wise men talk because they have something to say, however
on Thu, Dec 28, 2006 at 08:31 , Stephan Wehner just had 
to say something so we heard:

> >So login to the FreeBSD machine and trace back to your client IP -
> >or as close as you can get.  That may mean just to the edge of your
> >current provider but that may give you some idea.

> Ok, here is the result.

> $ traceroute 64.114.83.92
> traceroute to 64.114.83.92 (64.114.83.92), 64 hops max, 40 byte packets

> 1  VPS-18-137.virtualprivateservers.ca (65.110.18.137)  1.098 ms
> 0.991 ms  1.151 ms
> 2  a.core.65-110-0-1.van.data-fortress.com (65.110.0.1)  4.357 ms
> 1.557 ms  1.147 ms
> 3  64.69.87.37 (64.69.87.37)  1.740 ms  1.255 ms  1.150 ms
> 4  216.187.88.241 (216.187.88.241)  1.742 ms  2.438 ms  2.182 ms
> 5  204.239.129.214 (204.239.129.214)  1.910 ms  2.881 ms  3.489 ms
> 6  nwmrbc01dr02.bb.telus.com (154.11.4.72)  5.095 ms  3.309 ms  2.322 ms
> 7  64.114.45.106 (64.114.45.106)  6.555 ms  80.103 ms  9.048 ms
> 8  * * *
> 9  * * *
> 10  * * *
> 11  * * *
> 12  * * *
> 
> What does this tell??

Well there in no name associated with 64.114.45.106.  Whos shows
that is allocated to Telus Communications in Burnaby, British
Columbia.  The IP right before that is also a Telus IP.

So the next question is - what connects to 64.114.45.106.  Is that
an IP assigned to you and then you use NAT and/oa PAT to translate
to local address.  You target IP is in the same block
that Telos is allocated as they have 64.114.0.0 thru 64.114.255.255

The target IP does have a name associated with it and that
is zz83902.cipherkey.net.  Cipherkey.net is shown as being
located in Richmond BC.  Are they providing services for you.
If so you might check with them.

> By the way, other servers look "good". Meaning when I repeatedly
> access other websites (not my own) I don't see failures.

That sounds like throttling or as another poster said some
firewall/filtering taking place.   

I find the same problem as you do tracing to www.buckmaster.ca.
I can't traceroute to it as it stops resonding at 64.114.45.106, so
I'd say they are blocking things at that point - which isn't
helping at all :-( o

However the site comes up very fast.

Bill

> -- 
> Stephan Wehner
> >http://stephan.sugarmotor.org
> >http://stephansmap.org
> >http://www.trafficlife.com
> >http://www.buckmaster.ca

-- 
Bill Vermillion - bv @ wjv . com


More information about the freebsd-net mailing list