Re: Diagnose co-location networking problem

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Stephan Wehner <stephanwehner@...>
Cc: <freebsd-net@...>, Matthew Hudson <fbsd@...>
Date: Thursday, December 28, 2006 - 5:46 pm

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:





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.


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


-- 
Bill Vermillion - bv @ wjv . com
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Diagnose co-location networking problem, Stephan Wehner, (Tue Dec 26, 10:45 pm)
Re: Diagnose co-location networking problem, Matthew Hudson, (Wed Dec 27, 6:18 pm)
Re: Diagnose co-location networking problem, Stephan Wehner, (Thu Dec 28, 2:08 am)
Re: Diagnose co-location networking problem, Matthew Hudson, (Thu Dec 28, 4:31 pm)
Re: Diagnose co-location networking problem, Stephan Wehner, (Tue Jan 2, 12:07 am)
Re: Diagnose co-location networking problem, Matthew Hudson, (Thu Jan 4, 3:34 pm)
Re: Diagnose co-location networking problem, Stephan Wehner, (Fri Jan 5, 2:33 am)
Re: Diagnose co-location networking problem, Gary Palmer, (Thu Dec 28, 1:31 pm)
Re: Diagnose co-location networking problem, Bill Vermillion, (Thu Dec 28, 8:07 am)
Re: Diagnose co-location networking problem, Stephan Wehner, (Thu Dec 28, 12:31 pm)
Re: Diagnose co-location networking problem, Bill Vermillion, (Thu Dec 28, 5:46 pm)
Re: Diagnose co-location networking problem, Bill Vermillion, (Wed Dec 27, 9:45 am)
Re: Diagnose co-location networking problem, Stephan Wehner, (Wed Dec 27, 1:55 am)