2 edits |
[GA] Packet loss with SB6120Hey guys, I'm in central Georgia and upgraded from a Linksys BEFCMU10 to a Motorola SB6120 today. Installed the new modem around 3:30pm and been monitoring performance all evening. Things aren't looking too good. Ping tests come back with 30% packet loss and web pages rarely fully load (usually end up with several red X boxes where images are supposed to be). Thinking of going back to the BEFCMU10, but wanted to get your opinions first.
The modem started out with firmware 1.0.1.8 and CoxTech1 took me down to 1.0.1.7. Still experienced the problems, so he took me up to 1.0.2.4. Things haven't gotten any better.
Here are my modem stats:
Channel ID 17 Frequency 855000000 Hz Signal to Noise Ratio 37 dB Downstream Modulation QAM256 Power LevelThe Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading -5 dBmV
Upstream Bonding Channel Value Channel ID 2 Frequency 23696000 Hz Ranging Service ID 1140 Symbol Rate 2.560 Msym/sec Power Level 47 dBmV Upstream Modulation [3] QPSK [2] 16QAM [3] 64QAM
Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value Channel ID 17 Total Unerrored Codewords 69608054 Total Correctable Codewords 0 Total Uncorrectable Codewords 1346
I'd like to get this modem working since Docsis 3.0 is the next standard. Just wondering if I should call a tech to check the line or if I should send the modem back for a replacement (bad modem?).
Thanks!
Edit: Okay, this is the 5th time I've tried to submit this post. *crossing fingers* |
|
|
needforspeed59Cruise Ship Just Passing Through join:2001-05-02 La Place, LA |
Did you try without the router? |
|
|
Yes |
|
Ikyuao join:2007-02-26 Wichita, KS |
to LordFlux
Could you start running the traceroute to show it any the hop points of latency and packet loss problems? |
|
|
Tracing route to google.com [74.125.47.147] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1 2 5 ms 6 ms 5 ms 10.0.16.1 3 8 ms 8 ms 8 ms 68.1.8.49 4 8 ms 7 ms 8 ms 68.1.8.69 5 43 ms 42 ms 42 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142] 6 53 ms 53 ms * 72.14.233.65 7 54 ms 55 ms 53 ms 72.14.238.243 8 57 ms 56 ms 58 ms 209.85.254.241 9 69 ms 70 ms 74 ms 209.85.253.169 10 53 ms 54 ms 53 ms yw-in-f147.1e100.net [74.125.47.147]
Tracing route to dslreports.com [209.123.109.175] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1 2 8 ms 7 ms 10 ms 10.0.16.1 3 8 ms 8 ms 7 ms 68.1.8.1 4 30 ms 55 ms 29 ms 68.1.8.65 5 48 ms 47 ms 47 ms ashbbbrj01-ae3.0.r2.as.cox.net [68.1.2.210] 6 54 ms 54 ms 49 ms 0.e2-19.tbr1.ewr.nac.net [209.123.11.17] 7 43 ms 45 ms 46 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122] 8 54 ms 55 ms 56 ms vlan804.esd1.oct.nac.net [209.123.10.2] 9 36 ms * 49 ms www.dslreports.com [209.123.109.175]
Tracing route to yahoo.com [98.137.149.56] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1 2 7 ms 6 ms 8 ms 10.0.16.1 3 19 ms 20 ms 20 ms 68.1.8.1 4 12 ms 13 ms 19 ms 68.1.8.65 5 42 ms 173 ms 41 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142] 6 87 ms 86 ms 195 ms as-1.pat2.pao.yahoo.com [216.115.101.130] 7 89 ms 86 ms 87 ms ae-0-d141.msr1.sp1.yahoo.com [216.115.107.51] 8 88 ms 97 ms 89 ms te-9-1.bas1-1-prd.sp2.yahoo.com [67.195.128.249]
9 92 ms 95 ms 87 ms ir1.fp.vip.sp2.yahoo.com [98.137.149.56] |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-14 8:48 pm
everything looks like it is good to go and please run the pathping utility program that comes with your windows OS supplied that should show the visual of a path and that should show some sign of packet loss (packet dropping) and some latency problems produced... |
|
|
I just did a pathping to dslreports.com
Tracing route to dslreports.com [209.123.109.175] over a maximum of 30 hops: 0 Bio [192.168.2.15] 1 192.168.2.1 2 10.0.16.1 3 68.1.8.1 4 68.1.8.65 5 ashbbbrj01-ae3.0.r2.as.cox.net [68.1.2.210] 6 0.e2-19.tbr1.ewr.nac.net [209.123.11.17] 7 0.e1-4.tbr1.oct.nac.net [209.123.10.122] 8 vlan804.esd1.oct.nac.net [209.123.10.2] 9 www.dslreports.com [209.123.109.175]
Computing statistics for 225 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Bio [192.168.2.15] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1 0/ 100 = 0% | 2 6ms 0/ 100 = 0% 0/ 100 = 0% 10.0.16.1 1/ 100 = 1% | 3 13ms 9/ 100 = 9% 8/ 100 = 8% 68.1.8.1 0/ 100 = 0% | 4 11ms 8/ 100 = 8% 7/ 100 = 7% 68.1.8.65 0/ 100 = 0% | 5 29ms 12/ 100 = 12% 11/ 100 = 11% ashbbbrj01-ae3.0.r2.as.cox.net [68 .1.2.210] 3/ 100 = 3% | 6 34ms 13/ 100 = 13% 12/ 100 = 12% 0.e2-19.tbr1.ewr.nac.net [209.123. 11.17] 0/ 100 = 0% | 7 35ms 11/ 100 = 11% 0/ 100 = 0% 0.e1-4.tbr1.oct.nac.net [209.123.1 0.122] 3/ 100 = 3% | 8 34ms 14/ 100 = 14% 0/ 100 = 0% vlan804.esd1.oct.nac.net [209.123. 10.2] 1/ 100 = 1% | 9 33ms 15/ 100 = 15% 0/ 100 = 0% www.dslreports.com [209.123.109.17 5]
Trace complete. |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-14 9:23 pm
Coxtech1 should notice that some packet loss in the internal Cox networks, Cox have no control over beyond external networks as the point of external network have some packet loss but again, Cox have no control over it. |
|
|
Thanks, Ikyuao. I came over to my mother-in-laws house to get some work done. I submit MediCaid claims online and they kept timing out at home. Maybe we can figure this problem out and if not, I'll go back to the BEFCMU10 which ran with no problems. |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-14 9:49 pm
Try BEFCMU10 cable modem and run it and see if there are no further problems? |
|
|
Well things are running much better this morning. It looks like I have a new IP address, so a tech must've looked at it... thanks whomever it was! ^_^
Tracing route to dslreports.com [209.123.109.175] over a maximum of 30 hops: 0 Bio [192.168.2.15] 1 192.168.2.1 2 10.0.16.1 3 68.1.8.49 4 68.1.8.69 5 ashbbbrj01-ae3.0.r2.as.cox.net [68.1.2.210] 6 0.e2-19.tbr1.ewr.nac.net [209.123.11.17] 7 0.e1-4.tbr1.oct.nac.net [209.123.10.122] 8 vlan804.esd1.oct.nac.net [209.123.10.2] 9 www.dslreports.com [209.123.109.175]
Computing statistics for 225 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Bio [192.168.2.15] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1 0/ 100 = 0% | 2 6ms 0/ 100 = 0% 0/ 100 = 0% 10.0.16.1 0/ 100 = 0% | 3 9ms 0/ 100 = 0% 0/ 100 = 0% 68.1.8.49 0/ 100 = 0% | 4 11ms 0/ 100 = 0% 0/ 100 = 0% 68.1.8.69 0/ 100 = 0% | 5 28ms 0/ 100 = 0% 0/ 100 = 0% ashbbbrj01-ae3.0.r2.as.cox.net [68 .1.2.210] 0/ 100 = 0% | 6 35ms 0/ 100 = 0% 0/ 100 = 0% 0.e2-19.tbr1.ewr.nac.net [209.123. 11.17] 0/ 100 = 0% | 7 35ms 0/ 100 = 0% 0/ 100 = 0% 0.e1-4.tbr1.oct.nac.net [209.123.1 0.122] 0/ 100 = 0% | 8 33ms 0/ 100 = 0% 0/ 100 = 0% vlan804.esd1.oct.nac.net [209.123. 10.2] 0/ 100 = 0% | 9 34ms 0/ 100 = 0% 0/ 100 = 0% www.dslreports.com [209.123.109.17 5]
Trace complete. |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-15 4:14 pm
great. here you go and have fun with lagless now ^_^ |
|
1 edit |
Well since this thread is already open, and i decided to run pathping on my connection pinging both Cox.net, and dslreports.com. Just to see what my results would be, I don't know what these results exactly mean, and if its bad that 5 hop's just show 100. Btw I direct connected to pc, and no firewalls or anything to disturb the test. Here are the results, and are these fine?
C:\>pathping -n dslreports.com
Tracing route to dslreports.com [209.123.109.175] over a maximum of 30 hops: 0 24.254.xxx.xxx 1 10.12.160.1 2 68.10.14.125 3 172.22.48.137 4 172.22.48.165 5 172.22.48.129 6 * 68.10.14.17 7 68.1.0.220 8 209.123.11.17 9 209.123.10.122 10 209.123.10.2 11 209.123.109.175
Computing statistics for 275 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 24.254.xxx.xxx 0/ 100 = 0% | 1 --- 100/ 100 =100% 100/ 100 =100% 10.12.160.1 0/ 100 = 0% | 2 8ms 0/ 100 = 0% 0/ 100 = 0% 68.10.14.125 0/ 100 = 0% | 3 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.137 0/ 100 = 0% | 4 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.165 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.129 0/ 100 = 0% | 6 9ms 0/ 100 = 0% 0/ 100 = 0% 68.10.14.17 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% 68.1.0.220 0/ 100 = 0% | 8 22ms 0/ 100 = 0% 0/ 100 = 0% 209.123.11.17 0/ 100 = 0% | 9 22ms 0/ 100 = 0% 0/ 100 = 0% 209.123.10.122 0/ 100 = 0% | 10 23ms 0/ 100 = 0% 0/ 100 = 0% 209.123.10.2 0/ 100 = 0% | 11 22ms 0/ 100 = 0% 0/ 100 = 0% 209.123.109.175
Trace complete.
C:\>pathping -n cox.net
Tracing route to cox.net [68.1.17.9] over a maximum of 30 hops: 0 24.254.xxx.xxx 1 10.12.160.1 2 68.10.14.125 3 172.22.48.137 4 172.22.48.165 5 172.22.48.129 6 68.10.14.17 7 68.1.1.121 8 68.1.16.69 9 * 68.1.17.9
Computing statistics for 225 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 24.254.xxx.xxx 0/ 100 = 0% | 1 --- 100/ 100 =100% 100/ 100 =100% 10.12.160.1 0/ 100 = 0% | 2 7ms 0/ 100 = 0% 0/ 100 = 0% 68.10.14.125 0/ 100 = 0% | 3 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.137 0/ 100 = 0% | 4 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.165 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.129 0/ 100 = 0% | 6 9ms 0/ 100 = 0% 0/ 100 = 0% 68.10.14.17 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% 68.1.1.121 0/ 100 = 0% | 8 22ms 0/ 100 = 0% 0/ 100 = 0% 68.1.16.69 0/ 100 = 0% | 9 22ms 0/ 100 = 0% 0/ 100 = 0% 68.1.17.9
Trace complete.
Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>pathping -n cox.net
Tracing route to cox.net [68.1.17.9] over a maximum of 30 hops: 0 24.254.xxx.xxx 1 10.12.160.1 2 68.10.14.125 3 172.22.48.137 4 172.22.48.165 5 172.22.48.129 6 68.10.14.17 7 68.1.1.121 8 68.1.16.69 9 * 68.1.17.9
Computing statistics for 225 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 24.254.xxx.xxx 0/ 100 = 0% | 1 --- 100/ 100 =100% 100/ 100 =100% 10.12.160.1 0/ 100 = 0% | 2 7ms 0/ 100 = 0% 0/ 100 = 0% 68.10.14.125 0/ 100 = 0% | 3 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.137 0/ 100 = 0% | 4 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.165 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 172.22.48.129 0/ 100 = 0% | 6 8ms 0/ 100 = 0% 0/ 100 = 0% 68.10.14.17 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% 68.1.1.121 0/ 100 = 0% | 8 21ms 0/ 100 = 0% 0/ 100 = 0% 68.1.16.69 0/ 100 = 0% | 9 22ms 0/ 100 = 0% 0/ 100 = 0% 68.1.17.9
Trace complete. |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-15 7:51 pm
ICMP packets could be filtered out of it at each hops, on the based what they decided to set up a filtering against ICMP packets incoming.
Try surfing the webs on an internet over the TCP and any symptoms you are getting? |
|
|
said by Ikyuao:ICMP packets could be filtered out of it at each hops, on the based what they decided to set up a filtering against ICMP packets incoming. Try surfing the webs on an internet over the TCP and any symptoms you are getting? Well the internet runs fine it seems, But I have had upstream issue not to far back, and i still a notice alittle lag spike while gaming from time to time. I am just wondering why when trying to ping them 5 addresses it times out. Could this affect internet usage with it timing out like that though? I'm not here to complain more, but it has me wondering because its times out on them same 5 hops every pathping i run, which is the same 5 ip's. |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-15 8:03 pm
ping utility uses ICMP packet and you are pinging to them are timing out that reasons is that they configured the filter to drop the ICMP packets away and gaming online uses UDP that you are seeing the lag spiking that could be UDP is lost packets out of the order delivery as be aware that UDP is not guaranteed how that UDP packets are sent out and do nothing anything, while UDP packets are traveling the internet networking cannot be known. |
|
|
Ok gotcha, I just thought I would ask, because I don't know everything, and I know you guys will help me understand things sometimes I have no clue about. Anyways you are probably right, with cox running some kind of filter on them hops, anyways thanks again for the info . |
|
Ikyuao join:2007-02-26 Wichita, KS |
Ikyuao
Member
2010-May-15 8:19 pm
Welcome, you are eager to learn about the internet protocols? |
|
|
to lilstone87
It's not a filter so much as it is de-prioritizing certain types of packets. I always trace using an open source tool that uses TCP packets. That way, I know the results won't be affected by deprioritization. The only Windows equivalent I can find is here: » tracetcp.sourceforge.net/There's no recent activity on the project and I've never tried it so your mileage may vary. |
|
1 edit |
said by Ikyuao:Welcome, you are eager to learn about the internet protocols? Well not really at this point. I know this has nothing to do with your question. But I first came to this site when I had a overloaded node issue, over a year ago, and I have learn alot more then I did when I first join this site. I visit this site regularly because I do enjoy learning about other things, and helping others out that have problems I know alittle about. But there are times when you guy's talk about stuff I have no clue about, and I just read, and stay out of it. Because I'm not someone who gunna try and act like I know about something I have no clue about. I really just care about having a reliable internet connection, But in the process of trying to have one, I have meet alot of cool users on this site, and I'm greatful for all the help, and understanding everyone here has . |
|
chuckkk join:2001-11-10 Warner Robins, GA |
to LordFlux
A big change from earlier in the week! This is actually fairly decent for this area in GA
WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done checking for firewalls . . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client-to-server [C2S]) . . . . . 3.05Mb/s running 10s inbound test (server-to-client [S2C]) . . . . . . 12.22Mb/s
------ Client System Details ------ OS data: Name = Windows 7, Architecture = x86, Version = 6.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_17
------ Web100 Detailed Analysis ------ 45 Mbps T3/DS3 link found. Link set to Full Duplex mode Information: throughput is limited by other network traffic. Good network cable(s) found Normal duplex operation found.
Web100 reports the Round trip time = 85.23 msec; the Packet size = 1460 Bytes; and There were 47 packets retransmitted, 931 duplicate acks received, and 860 SACK blocks received The connection was idle 0 seconds (0%) of the time S2C throughput test: Packet queuing detected: 61.96% This connection is sender limited 39.71% of the time. This connection is network limited 60.22% of the time.
Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ON RFC 896 Nagle Algorithm: ON RFC 3168 Explicit Congestion Notification: OFF RFC 1323 Time Stamping: OFF RFC 1323 Window Scaling: ON
Server 'jlab4.jlab.org' is not behind a firewall. [Connection to the ephemeral port was successful] Client is probably behind a firewall. [Connection to the ephemeral port failed] Packet size is preserved End-to-End Server IP addresses are preserved End-to-End Information: Network Address Translation (NAT) box is modifying the Client's IP address Server says [98.184.xxx.xxx] but Client says [192.168.0.xxx] |
|
|
to LordFlux
LordFlux, if you will IM your MAC address to MGA_SOC we will be happy to take a look at this probelm for you. |
|
1 edit |
said by MGA_SOC:LordFlux, if you will IM your MAC address to MGA_SOC we will be happy to take a look at this probelm for you. Thanks, MGA_SOC! I connected my new cable modem up Friday afternoon and by Saturday morning, the problems were fixed. I had obtained a new IP address sometime during the night. Not sure if that's what fixed it or if there was something else going on. Been running like a champ since! There are no more signs of packet loss and this modem is considerably faster than my old BEFCMU10. Like I was telling CoxTech1, my XBox 360 used to have mini-pauses when accessing online content... now it accesses smoothly and there are no more stutters or pauses. I'm very satisfied and loving the speed/responsiveness of this new modem. |
|
|
We are glad to hear your service looks to be working properly. Please let us know if you see any new signs of significant packet loss. |
|
chuckkk join:2001-11-10 Warner Robins, GA |
Sadly, today started out good. As the evening approached, a series of tests showed deterioration and mixed results to "long haul" destinations. Some seem to have the upload & download speed "limits" reversed. In most cases, upload speeds met my class of service. Download speeds were more uneven, with a few locations showing low upload and down load speeds. |
|