  jparn1
join:2002-01-29 Oklahoma City, OK
| reply to AirP Re: Latency in Oklahoma City
I am a gamer AirP, but from the looks of the tests, I am having better luck than u are. I play most of the popular FPS and also car racing sims. I have had pretty good luck gaming for about the last 10 days or so. I understand about packet loss. Gaming online has been pitiful for me for about the last 6 months. I do get a break sometimes. Usually I get lag and disconnects that goes on for several weeks at a time. It is showing improvement lately. Good luck with yours. S.W.OKC. |
|
  jparn1
join:2002-01-29 Oklahoma City, OK
| reply to cinnamon Hey cinnamon, I am close to the switch for SWBell DSL. I had SWBell DSL before changing to Cox and I experienced similiar problems until I fired Bell and hired Cox. That is why I am reluctant to change again. I might be jumping from the frying pan to the fire, and Bell is a year contract unless they had a policy change. I keep hoping that Cox will get it together. I guess I will start posting on Zar's string? I check Atlanta because I think that is where Cox hangs their hat. I am trying to keep cool and wait and see. Good Luck,J.P. S.W.OKC. [text was edited by author 2002-06-10 16:33:00] |
|
  cinnamon How Smart Is Your Card? Premium join:2002-01-19 Tulsa, OK
| reply to jparn1 SWBell's DSL isn't really an option for me. At least not until they move one of their COs about 2 miles out. It is either Cox Half Speed Internet, or dial up.
You show a speedtest result of 2584/267 to Atlanta. I don't remember getting anything over 2000 while on Cox. @Home let me go that fast. At one point I did many pings, traceroutes and speedtests, and discovered that Boston was actually my "closest" speakeasy.net speedtest site. It even beat Cox's Atlanta home turf.
(P.S. This thread doesn't look locked to me. Zar didn't even have anything to report when starting a new thread. Go figure.) |
|
 AirP Premium join:2002-06-08 Oklahoma City, OK
| reply to jparn1 Better then 56K? That depends on what you're using it for. If you're a gamer, the packetloss can basicly kill you, if you're just viewing webpages/ftping, it's still good.
I'm on Cox HSI and I'm actually playing my online line games with Netzero again(and looking for a cheaper Dialup ISP), does that tell you anything about what type of service I'm getting from Cox?
People using Cox for not continous streaming from the internet are fine, those who want to game or SSH into other machines to do actual work have an extreamly hard time justifying paying 35 a month for something that just fustrates the crap out of them. |
|
  jparn1
join:2002-01-29 Oklahoma City, OK
| reply to cinnamon Hey cinnamon, I have been seeing some rough line quality tests for the last couple of days, hope it is not the start of the same old roller coaster ride. Here is this mornings test at about 9:40am central, 6/10/2002. »/quality/nil/780781 Here are some speed tests: 2002-06-10 11:12:36 Speed test (lax.speakeasy.net) 1479/268 kbps 2002-06-10 11:11:40 Speed test (nyc.speakeasy.net) 1222/268 kbps 2002-06-10 11:10:39 Speed test (chi.speakeasy.net) 1603/251 kbps 2002-06-10 11:09:44 Speed test (atl.speakeasy.net) 2584/267 kbps
Cox sure has not lived up to their promises this year, but they are still better than 56k. I wish SWBell DSL was not a year contract, or I think I would give them another chance. I may yet. S.W.OKC. [text was edited by author 2002-06-10 11:15:26] |
|
  cinnamon How Smart Is Your Card? Premium join:2002-01-19 Tulsa, OK
| reply to AirP The ping plot is to the Cox router I was seeing problems with yesterday. I wonder how many times 68.12.9.5 took over 1 and a half seconds to respond?
This morning, things seem to be a little quieter. »/quality/nil/780731
Speeds back to Half (1500/270). |
|
 AirP Premium join:2002-06-08 Oklahoma City, OK
| reply to cinnamon Sorry for posting my IP, even with it a known it still would be as fustrating to them to get to my machine as it is for me trying to use the internet.
Since this is happening every 20-30 seconds, the huge if not total packet loss for a few seconds, is there a way that if radar was too close to a switch or server it could cause major disruption, I know when I worked in the USAF that if you had a radio on, it would be disrupted every 20-30 seconds because of the radar rotation... |
|
  cinnamon How Smart Is Your Card? Premium join:2002-01-19 Tulsa, OK
| reply to jparn1 I thought that I might see how well my system is tweaked, but saw "Trial ping gave errors: Time Exceeded" in my results »ny-monitor.dslreports.com/tweak/···a=normal.
Gee, that's odd. I wonder what's going on. Did a Line Quality: »/quality/nil/780488. A little bit of going up and down a hill from the 'ec', but a pretty one-sided ramp from the 'wc'. It looked so much better at 8:30 am this morning. »/quality/nil/779932
EDIT: Speed test results to go along with this havoc: 808/282.
P.S. Gee, I'm sorry. It is beginning to get a little aggravating waiting and watching in East Tulsa. I don't know if I should tweak my system for Cox, or start saving my money for retirement. I've heard that once one tries out broadband (cable or dsl), one will never return to dial-up. That myth has been tested by others in this forum. I want my broadband working smoothly and quickly, you know, like how things were with @Home? You remember, how Cox promised everything would be great, and nothing would be diminished?
P.P.S. You'll need to "REPLY TO THIS" rather than use the big "POST REPLY" button at the bottom of the page. If you don't you'll see the following in a yellow box: "Warning:This topic is too old to reply to. Please press BACK." [text was edited by author 2002-06-10 08:13:25] |
|
  jparn1
join:2002-01-29 Oklahoma City, OK | reply to Zar 9:30pm central 6/9/2002 »/quality/nil/780430 This does not look good! S.W.OKC. |
|
  Zar Premium join:2001-08-04 Platte City, MO | reply to Micheal64 »/quality/nil/780105 |
|
  jparn1
join:2002-01-29 Oklahoma City, OK
| reply to 2kmaro Still looking pretty good at my house. Online gaming working too. »/quality/nil/779978 test performed 9:15 am central 6/9/2002 I hope this continues. Line quality test at noon 6/9/2002 »/quality/nil/780088 This test does not look so good! Speed tests 6/9/2002 2002-06-09 12:51:06 Speed test (lax.speakeasy.net) 2133/268 kbps 2002-06-09 12:50:16 Speed test (sfo.speakeasy.net) 2310/268 kbps 2002-06-09 12:49:27 Speed test (dslcheck.speakeasy.net) 760/268 kbps 2002-06-09 12:48:14 Speed test (wdc.speakeasy.net) 1546/273 kbps 2002-06-09 12:46:52 Speed test (nyc.speakeasy.net) 2280/268 kbps 2002-06-09 12:46:06 Speed test (dfw.speakeasy.net) 1318/267 kbps 2002-06-09 12:45:04 Speed test (den.speakeasy.net) 2402/268 kbps 2002-06-09 12:44:16 Speed test (chi.speakeasy.net) 1579/268 kbps 2002-06-09 12:43:21 Speed test (atl.speakeasy.net) 2369/268 kbps S.W.OKC.
[text was edited by author 2002-06-09 13:25:48] |
|
 NukeDukem
join:2002-05-21 Tulsa, OK
| reply to Micheal64 I got tired of the instability with Cox's network and decided someone local could probably do it right. Switched to Tulsaconnect DSL and it is great 1.5Mbps down / 256kbps up ADSL service is what I got.
Cox's max download speeds were higher, but not worth the connectivity issues. I would constantly get disconnected from AIM, IRC, continuously the entire night.
Any server on Tulsaconnect's network I get an 8-10ms ping to (This includes my mail servers, news server, name servers, etc) and it never fluctuates. They are also extremely responsive on a customer service level. You can call or email and immediately get an answer  |
|
  vtechgsx8
join:2001-04-07 Fairfax, VA
| reply to Zar Can someone from OKC tell me if they see lots of arp traffic on their network? Out here in Fairfax, VA the data light is constantly on. Checked out what was happening and all of it is arp traffic from the gateway. On the order of 5-12 / sec. I'm looking at Zar's packet sniff and seeing that you don't have this problem. Just wondering if its normal or not. Thanks.
said by Zar: Getting hammerd by some multicast crap.
I wish cox could filter this, my modem light is flashing like crazy.
|
|
  Zar Premium join:2001-08-04 Platte City, MO
| reply to Micheal64 Here is a text file of a pingplot tonight. |
|
  Zar Premium join:2001-08-04 Platte City, MO
| reply to Micheal64 Getting hammerd by some multicast crap.
I wish cox could filter this, my modem light is flashing like crazy. -- Don't knock on deaths door, ring the bell and run, he hates that. |
|
  cinnamon How Smart Is Your Card? Premium join:2002-01-19 Tulsa, OK
| reply to Micheal64 The results from 'ping -l 1472 -n 250' to gateway IP:Ping statistics for 10.1.176.1: Packets: Sent = 250, Received = 249, Lost = 1 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 224ms, Average = 59ms
Small roller coaster ride in the LQ ping plots. »/quality/nil/779668 |
|
  BillRoland Premium join:2001-01-21 Ocala, FL clubs:
·Cox HSI
| reply to 2kmaro Here is what I just got, and it looks pretty good: Ping statistics for 68.97.0.1: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 101ms, Average = 64ms -- "Do your duty in all things. You cannot do more. You should never wish to do less." Robert E. Lee |
|
  2kmaro Think Premium,ExMod 1 BC join:2000-07-11 ColossalCave clubs:  
| reply to BillRoland Not at all - no problem as far as I'm concerned. We've all got to cover one another's butts when we can. It's just a bit easier for me than you in cases like this.
You might also try the trick I did: hit a couple of those points with a bunch of 128 or larger ping packets and see if you don't get those huge spikes like I did. If you review some of the tracerts of late, you'll see the 3 or 4 points that are almost consistently above 100-150ms or worse, and they are points that I think would affect a large number of users. -- Waste is such a terrible thing to mine. |
|
  BillRoland Premium join:2001-01-21 Ocala, FL clubs:
·Cox HSI
| reply to 2kmaro Sorry 2k, I guess in my eagerness to show him the clean trace, I wasn't thinking when I posted that. I will hide IP addresses like that in the future. Would you mind if I re-upload a "corrected" version of the plot? [text was edited by author 2002-06-08 19:34:52] |
|
  2kmaro Think Premium,ExMod 1 BC join:2000-07-11 ColossalCave clubs:  
| reply to AirP A couple of things: first, not always safe to post your IP in a public place like this, so I've gotten rid of it in your post and in Bill Roland's reply.
I then pinged your gateway (68.97.0.1) and noticed a couple of interesting things: For the most part the pings were in pretty good shape, around 19 to 22 ms for much of the time, with every once in a while jumping up into 30s or even 40s, then WHAM! there was one with a 1516 ms latency! That's 1 and a half seconds. Not good for a gateway. The summary looked like this:
Ping statistics for 68.97.0.1: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 1516ms, Average = 37ms What you need to do/where you need to start is with that gateway. Hammer that rascal a couple of times a day - during light traffic times and heavy. Make sure your results go to a file where you can retrieve them to show to Cox. If you're unfamiliar with the "ping" command here is how to do it:
Open the MS-DOS window, either from the Start/Programs bar or by using RUN and entering "Command.com".
Use a command format like this: ping -n 100 -l 1440 68.97.0.1 >> c:\windows\temp\mygateway.txt
what will happen is that your system will start pinging that address 100 times with 1440 byte packets (that is a dash ell, not dash one) and it will keep sending the results of that test and any subsequent ones to the file named after the >>. The >> says append this to that file if it exists, start new file if it doesn't. So, all of your results are going into that single file. You can then use Notepad.exe or wordpad.exe to examine the file and find any huge latency times.
If you prefer to put each test into a separate file, use a command like: ping -n 100 -l 1440 68.97.0.1 > c:\windows\temp\Test_01.txt and change the "_01" to "_02", "_03" etc for each test.
While the test is running and results are being sent to the file, the cursor will just sit and flash. When it is done, you'll get the C:\ prompt back.
If you want to just see how things are doing for the moment, try the command without the > or >> and filename, as
ping -n 50 -l 1440 68.97.0.1 and the results will be displayed on your monitor. -- Waste is such a terrible thing to mine. |
|