Re: [Nolug] Request for a Cox user...

Jeremy (mailing list box) wrote:
>> 11 ashbbbpc01gex0200a100.r2.nv.cox.net (68.105.30.30) 21 ms 19 ms
<...>
> Physical distance wise, there's no way you should be seeing 20ms if you
> go from NOLA, to Baton Rouge, to Dallas and then back east through
> Ashburn... There should be a much greater difference between hop 10
> and 11 if those routers are in the locations where they say they are
> located and the packets are actually following that route.
>

That #11 hop is in nevada (nv.cox.net). the hostname portion doesn't refer to
any city of ashburn on the east coast. Cox doesn't always seem to name things
that way in the hostname. While mctydsrc01-gew03010999.rd.no.cox.net appears
to refer to a Cox location in Mid City in New Orleans and
btnrbbrc02-pos0102.rd.br.cox.net refers to Baton
Rouge,lkhnbbrc02-pos0102.rd.at.cox.net for Atlanta looks kinda funny. Until you
  look at Cox's headquarters address and see it's on "Lake Hearn Drive" in
Atlanta (http://www.cox.com/about/headquarters.asp). Everybody's got their own
naming conventions and you really can't read that much regarding geography into
  it.

incidentally, I get ~80ms RTT to your packet8 proxy addess on my cox connection
that routes through Atlanta. Your traceroutes show ~60ms RTT going to the same
location so you will lose a bit. The question is whether or not that
difference would impact your packet8 VOIP service in a noticeable way. I've
been using Vonage on Cox for some time without problem. I've also used Skype to
call overseas and the quality was excellent.

-- 
Scott Harney <scotth@scottharney.com>
"Asking the wrong questions is the leading cause of wrong answers"
gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
___________________
Nolug mailing list
nolug@nolug.org