how-to block ads
|
JJ Beaver
@spiritbb.com
| Spirit Broadband, packet loss, and me (east TN)
I switched from Frontier DSL to Spirit Broadband Cable.
For the past 2-3 months, i have been experiencing pretty rotten packet loss. I am an avid World of Warcraft gamer, so as you can imagine, this causes plenty of frustration.
Some things you should know about Spirit Broadband... on the 4th hop of a tracert, it jumps right into the Charter backbone. At first, i thought it was Charter's problem.. i'd do pingpath and tracerts, getting timeouts and 10%-20% packet loss from Charter nodes and all nodes, really. A neighbor of mine (about 50 yards from where i live) is experiencing similar problems.
this packet loss/connectivity issues seems to happen at very random times. could happen at 3am... could happen at 2pm.
Anyway, i read up on powerlevels of cable modems, and i'm starting to think my packet loss is due to my powerlevels. Anyway, have a look, and i'll include a tracert as well. Oh yeh, and the event log on the cable modem is spewing alerts during the packet loss period. it is VERY intermittent.
Tracing route to worldofwarcraft.com [12.129.242.22]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * 7 ms * ms x.xxx.x.x
3 * 8 ms 81 ms gw.spritbb.com [x.xxx.xxx.x]
4 15 ms 13 ms 15 ms 68-119-96-201.static.jcsn.tn.charter.com [68.119
.96.201]
5 14 ms 17 ms * 96-34-71-62.static.kgpt.tn.charter.com [96.34.71
.62]
6 * 26 ms 23 ms static.unknown.charter.com [96.34.79.76]
7 25 ms 26 ms * static.unknown.charter.com [96.34.79.62]
8 34 ms 34 ms 37 ms crr01sghlga-tge-0-0-0-6.sghl.ga.charter.com [96.
34.78.18]
9 * 35 ms 35 ms 96.34.78.89
10 36 ms 34 ms 33 ms bbr02sghlga-tge-0-0-0-6.sghl.ga.charter.com [96.
34.2.46]
11 37 ms 35 ms 42 ms atx-edge-02.inet.qwest.net [65.124.15.33]
12 47 ms 34 ms 35 ms atl-core-02.inet.qwest.net [205.171.21.9]
13 35 ms 35 ms 35 ms atx-brdr-01.inet.qwest.net [67.14.14.102]
14 36 ms 35 ms 39 ms 192.205.35.241
15 88 ms 87 ms 88 ms cr1.attga.ip.att.net [12.122.89.30]
16 90 ms 88 ms 87 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 88 ms 89 ms 89 ms cr2.la2ca.ip.att.net [12.122.28.178]
18 88 ms * 89 ms gar5.la2ca.ip.att.net [12.122.129.25]
19 89 ms 88 ms 88 ms 12.122.255.74
20 88 ms 89 ms 87 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
21 * * * ---- reached WoW's firewall
-----------------------------------------------------
ARRIS DOCSIS 1.1 / SIP 2.0 Touchstone Telephony Modem HW_REV: 04
VENDOR: Arris Interactive, L.L.C.
BOOTR: 6.03
SW_REV: 5.2.67T.SIP
MODEL: TM602A
Downstream
Freq/Power: 579.000 MHz 13 dBmV
Signal to Noise Ratio: 35 dB
Modulation: QAM64
Upstream
Freq/Power: 26.992 MHz 32 dBmV
Channel Type: DOCSIS 1.x (TDMA)
Symbol Rate: 2560 kSym/sec
Modulation: QAM16
-----------------------------------------------------------
Event Log:
9/25/2009 0:08 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
9/25/2009 0:09 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
9/25/2009 0:09 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
9/25/2009 0:09 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
9/25/2009 0:09 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
9/25/2009 0:09 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
9/25/2009 0:09 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
9/25/2009 0:09 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
9/25/2009 0:09 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
9/25/2009 0:09 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
9/25/2009 0:09 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
9/25/2009 0:11 20000200 3 No Ranging Response received - T3 time-out
9/25/2009 0:12 13000100 3 DHCP FAILED - Discover sent, no offer received
9/25/2009 0:47 20000200 3 No Ranging Response received - T3 time-out
--------------------------------------------
Thanks again folks, any advice you can give me would be most appreciated. | |
dbmvTechs
join:2009-10-04
2 edits | bump | |
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to JJ Beaver
said by JJ Beaver :
20 88 ms 89 ms 87 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
I don't see any packet loss. All trace packets sent to this router have a return packet; for zero packet loss.
Nearly 90 ms from Tennessee to Los Angeles, California. Pretty good RTT, actually.
If you are seeing problems with ping within the game, that can't always be determined by trace route. And WoW has had problems for other ISP customers, off and on.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
AskATech
join:2009-10-16
Keansburg, NJ
| reply to JJ Beaver
Your downstream is a little high at 13 but shouldnt cause a problem..your transmit is very borderline at 32...and DOCSIS 1.1 is behind technology were moving in to 3.0 here...on their own these may not be too much cause for concern but together i can see speed issues and possibly packet loss...but its easy to determine with someone who knows there way around a triolithic meter (a cable guy should)... use the internal modem in the meter and lock up on the cable...run a packet test on there if its clean you know its nothing on the cable or system...if there is packet loss its usually bad or loose connections jus got to trace it back until you do not get the loss....next to determine if its the modem keep the meter locked up on the cable still using the modem in the meter and connect with ethernet to the computer (this is y u need someone who knows their way around the meter an inexperienced tech would probably not know he can even do this), neway run packet test on the comp now with the meter modem if the loss is gone u need a new modem (unlikely), but if the loss is still there then you have eliminated everything else, except the computer and the server(s) you are pinging...so that being said have a cable guy come to exclude those things if he doesnt know what he is doin show him this post or tell him to call someone who does | |
cypherstream
Looking forward to the future of things.
Premium,MVM
join:2004-12-02
Reading, PA
clubs: | reply to JJ Beaver
Wow +13 forward and 32 return. Warm signal you got there. | |
-
|
