dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2451
share rss forum feed

Shadowdane

join:2000-11-02
Fairfax, VA

Packetloss on Cox's network - 68.1.4.139

I'm seeing a lot of packetloss on this router on Cox's network. A significant amount of websites for me are routed through this hop. So seeing lots of timeouts and drops in download speed when ever a website jumps through that route.

I'm seeing 50-75% packetloss just on that hop: 68.1.4.139
IP Lookup showed that IP range is on Cox's network:
Cox Communications Inc. NETBLK-AT-INT-68-1-0-0 (NET-68-1-0-0-1) 68.1.0.0 - 68.1.127.255

Traceroute example




Shina

@cox.net

Hello Shadowdane,

I'm having a similar problem in Arizona with a similar server, also my fifth hop to pretty much anywhere, with the IP 68.1.1.19. Same PingPlotter results. Have you tried pinging that IP directly in the Windows cmd ? When I do this with my questionable hop, the pings look normal. However, when I try to run a trace route to anywhere with Windows or PingPlotter, I get a lot of time-outs at this address.

For me, it seems that even if my Internet speeds are perfectly fine and stable, this hop will still show 40-50 % packet loss consistently on PingPlotter. It's to the point where I was wondering if it was an issue with PingPlotter and not the server itself, but I find it fascinating that you are posting about essentially the same observation.



Iceman0803

join:2012-05-18
Glendale, AZ
reply to Shadowdane

Being that there is no loss before or after that hop it's very likely that router deprioritizes ICMP packets. Basically, it only responds to a set number in a given time frame. Once that number is reached it discards the rest. Hope this helps.



CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76
reply to Shadowdane

Iceman0803's right, 68.1.4.139 can't be dropping packets if you're able to get to 70.167.150.18 and beyond without loss.



Iceman0803

join:2012-05-18
Glendale, AZ

said by CoxTech1:

Iceman0803's right, 68.1.4.139 can't be dropping packets if you're able to get to 70.167.150.18 and beyond without loss.

My knowledge is thanks to you Sir!

Shadowdane

join:2000-11-02
Fairfax, VA
reply to Shadowdane

ok I've figured out a bit more specifically when I'm getting packetloss... it seems when ever I'm downloading or uploading over maybe ~4-6Mbps sustained throughput. I start getting packetloss, once the bandwidth usage goes back to 0 the packetloss stops.

Like tonight for example I fired up Netflix on my Xbox 360 and started streaming a HD show which is about 4-5Mbps stream. I jumped on my computer and did a pinged youtube.com for example.




I only started having this problem when I upgraded to a SB6141 modem and the 100/20 package. I had no such issue with my SB6120 and the 30/3.5 package I had previously.

Signal levels look fine I think:



CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76

This data makes a little more sense now. The trace route you posted this time indicates loss between the PC you tested from and our CMTS. Can you try without the router and see if it's possible to duplicate these results?


phxuser

join:2010-03-16
Scottsdale, AZ
reply to Shadowdane

What firmware are you running on the SB6141? I had similar problems until the firmware was automatically upgraded by Cox to SB_KOMODO-1.0.6.8-SCM01-NOSH.



odog
Cable Centric Vendor Biased
Premium,VIP
join:2001-08-05
Atlanta, GA
kudos:11
Reviews:
·Comcast
reply to Shadowdane

said by Shadowdane:

ok I've figured out a bit more specifically when I'm getting packetloss... it seems when ever I'm downloading or uploading over maybe ~4-6Mbps sustained throughput. I start getting packetloss, once the bandwidth usage goes back to 0 the packetloss stops.

Sounds like QOS on the router is kicking in.

Manse

join:2013-01-25
Warner Robins, GA
reply to CoxTech1

said by CoxTech1:

This data makes a little more sense now. The trace route you posted this time indicates loss between the PC you tested from and our CMTS. Can you try without the router and see if it's possible to duplicate these results?

I am having similar problems when I route through either 68.1.4.139 or 68.1.4.133. I was supposed to have a tech come out Wednesday, but I received a call saying that the problem was fixed on Cox's end. I was still having terrible problems, on an unloaded line, last night after the fix.

I will upload pingplotter outputs when I get home tonight.

Manse

join:2013-01-25
Warner Robins, GA

Click for full size
Click for full size
Click for full size
As mentioned


CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76

The loss in your case appears to be mostly random. Can you try without the router and post the results?


Manse

join:2013-01-25
Warner Robins, GA

Apologies for the delay, been a long weekend.

Unless I'm missing something, it's not random. it's at one of two servers, depending on whether I ping google or something else.

Tonight's scan during a LoL game, in which I was reporting 225-250 ping in game. "normal" ping during the day is under 100 and when I'm having these packet problems it's usually around 180-200.

Feel in the game was marginally worse without the router.

Thoughts?


CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76

This second trace route without the router looks much better. 68.1.4.133 is showing ICMP deprioritization but no issues unlike the previous results you posted.


Manse

join:2013-01-25
Warner Robins, GA

1 edit

So how do I fix the deprioritization? Is that the cause of my latency/stutter?

I'm currently in game, sitting at over 200 ping. Hell, I'm an hour south of Atlanta and my ventrilo (tungsten.typefrag: in ATL) is pinging at 150+ ms.


KennyD

join:2005-03-08
Norfolk, VA

ICMP deprioritization is nothing to worry about. It isn't going to negatively affect your connection. As mentioned earlier, all that's happening is the router only replies to a certain number of pings within a given time frame. After that it just ignores the ICMP packets (ping) and that's why you see packet loss at 68.1.4.133 in Ping Plotter. This router isn't ignoring regular packets so that's why you don't see packet loss after that hop [68.1.4.133].

Hope that makes sense. Now as far as latency/stutter that is definitely a problem.. but it's not caused by 68.1.4.133 doing ICMP deprioritization.



CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76
reply to Manse

As KennyD See Profile mentioned ICMP deprioritization is a non-issue and won't cause any problems with your connection. Comparing your pingplotter results with and without the router leads me to believe the router may be a contributing factor with regards to the issues you're experiencing.


Manse

join:2013-01-25
Warner Robins, GA

I'll snag a new router tomorrow, but I still had the same issue in game.

Perhaps it's on LoL's end, but noone I play with has the same problem

updates with new router tomorrow.


Manse

join:2013-01-25
Warner Robins, GA

Click for full size
For reference, I found one of the server IPs from another thread. Ping Plotter (with router).

I'd like to get without the router, but SWMBO is using the tubes as well.


CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76

Your other ping plotters also looked better without the router so I would try this test again without it to compare the results.


Manse

join:2013-01-25
Warner Robins, GA

Click for full size
Click for full size
Click for full size
Bought a brand new router
With and without from tonight (in that order):

I'm at a loss, and the internet rage is building in me when I try to play games. Is there anything I can do?


CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76

The replacement router appears to have helped with some of the intermittent loss that was being observed previously. Latency is still a little high but still much better without the router. Which tier of service do you subscribe to and do you have any other Internet applications running?


Manse

join:2013-01-25
Warner Robins, GA

When the problem started, I upgraded to Premier in the vain hopes that it was a neighborhood bandwidth issue. I haven't stepped back down.

During these tests, the only programs I had running were Firefox (generic speed tests show 15-30Mbps download, Ventrilo, and LoL.

The vent was probably an interesting issue. my ping to tungsten.typefrag.com (located in Atlanta) was ~175 ms, to go maybe 100 miles north. My ping to the LoL servers (according to in game) was ~200-250, and they're west coast.

And again, it's time-related. I played one or two games when I got home with no problems. But once the sun goes down, my connection goes all Mr. Hyde on me.



CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:76

It may be necessary for a technician to come out and so some further troubleshooting at this point.


Manse

join:2013-01-25
Warner Robins, GA

Click for full size
Click for full size
Click for full size
Firstly, thanks for the help CoxTech1. I cleaned up some other stuff and that seemed to help the issue temporarily. However, I still lag like crazy in about 80% of games. The first two images were from really bad games, the third is from one that I only lagged the second half. In the third, is there anything I can do about the 150+ ping on the 6th and 7th hop. I know the answer, but I have to at least ask.

Should I still call for a tech?