US Cable Support > Bright House Networks > It's that time of the year again.. packet loss week 1.

It's that time of the year again.. packet loss week 1.

Please PM your modem Mac address and IP address and I'll take a look.

Same issue here, sporadic evening massive packet loss / lag which began last week. BH RR Lightning user in Clearwater area. Any ideas?

reply to JeffMD
Jeff I would like to get a tech out please pm your availability over the next couple of days. Nothing major but worthy of an onsite look.

reply to Mattingly

Sorry for the delay. So yes im not having the issue with anything except wow. ive done tracert and there seems to consistently be a spike in latency when it hits an at&t hop...

12 130 ms 128 ms 234 ms cr81.fldfl.ip.att.net [12.122.81.26]

there was a similar issue around march 2011, wow of course says it isnt anything on their end. any ideas would be greatly appreciated.
thanks.

reply to JeffMD
Post complete tracerts please and yes I am VERY aware of the issue last year (more than you will ever know). Since I don't have all the data it's premature to assume that this is the same 3rd party again....

yes i remember you helped a ton back then thats why im back and thank you!

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

1 1 ms 3 ms 4 ms tampabay.rr.com [192.168.1.1]
2 27 ms 15 ms 29 ms cpe-173-170-48-1.tampabay.res.rr.com [173.170.48.1]
3 27 ms 19 ms 19 ms 65.32.36.226
4 17 ms 20 ms 32 ms ge1-2-0.tampfledc-rtr4.tampflrdc.rr.com [65.32.13.33]
5 21 ms 14 ms 20 ms 72-31-208-0.net.bhntampa.com [72.31.208.0]
6 23 ms 19 ms 34 ms ae2-0-orld71-cbr1.bhn.net [72.31.220.1]
7 55 ms 51 ms 49 ms xe-11-3-0.bar1.Orlando1.Level3.net [4.79.116.137]
8 * 51 ms 48 ms ae-0-11.bar2.Orlando1.Level3.net [4.69.137.146]
9 61 ms 56 ms 52 ms ae-5-5.ebr2.Miami1.Level3.net [4.69.148.209]
10 55 ms 55 ms 53 ms ae-2-52.edge2.Miami2.Level3.net [4.69.138.109]
11 * * 140 ms 192.205.36.253
12 609 ms 130 ms * cr81.fldfl.ip.att.net [12.122.81.26]
13 975 ms 136 ms 132 ms cr2.ormfl.ip.att.net [12.122.1.45]
14 129 ms 128 ms 131 ms cr1.ormfl.ip.att.net [12.122.5.185]
15 657 ms 140 ms * cr2.hs1tx.ip.att.net [12.122.1.5]
16 144 ms * 130 ms cr1.dlstx.ip.att.net [12.122.28.157]
17 127 ms 128 ms 126 ms cr2.dlstx.ip.att.net [12.122.1.210]
18 167 ms 600 ms * cr2.la2ca.ip.att.net [12.122.28.178]
19 240 ms 264 ms 136 ms gar29.la2ca.ip.att.net [12.122.129.241]
20 133 ms 129 ms 130 ms 12-122-254-234.attens.net [12.122.254.234]
21 127 ms 126 ms 126 ms 12.129.193.250
22 12.129.211.38 reports: Destination net unreachable.

Trace complete

Alright lets keep an eye on this and I'll be looking for more examples. As you are aware from last time this was not a quick fix and involved a ton of work. Do me a favor and keep an eye out over at Bliz for other reports of this and copy me via PM. They must be current and complete....I can't waste time on "me toos" with no data and especially if you see others from our network. I'm going to spend time over there as well looking and we'll see how this goes....hopefully just a short term hiccup but I need to remind you this is off-net and these things can be complicated.
--
~All truth goes through three phases. First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as self-evident. - Einstein~

reply to JeffMD
Well it had cleared up by the time the tech came on monday and he replaced the drop line anyways as it looked pretty worn. Monday night raiding was wonderful, but unfortunately I came home tonight to find lots of packetloss again. This time the modem has really no errors to show for it either. I tested raiding on my laptop again to rule out the desktop. I'm pretty much out of ideas now and just hopes it clears up again. It seems to be purely network related and nothing to do with the cable.

reply to JeffMD
Nope... Jeff in your case it was signal related. I'll take a look today and see whats going on.

as you may have seen there are another 30+ posts scattered around and all the traces seem to show the same thing dealing with the chicago servers and at&t blah blah blah. the usual finger pointing "not-it" situation guess ill have to sit it out and wait. thanks though.

reply to JeffMD
Send me what ya find and I'll look at them closely....

reply to JeffMD
just a little heads up. The problem is pretty much gone again. I had a tech out and unfortunately I was no longer able to replicate the packet loss, and that night was fine. The following day was unplayable again but since that one day it has since been working fine.

reply to JeffMD
Keep me up to date please

reply to JeffMD
Well earlier today while watching sum football, my wow game suddenly got laggy and disconnecty again.. I decided to wait it out and retired to the bed to watch my giants play. I was on my laptop and I could still note the packetloss in non responsive clicks and file downloads. I just now decided to brows my cable modems log file...

yikes.

me ID Level Description
Mon Jan 23 02:44:14 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jan 23 02:36:54 2012 73040100 Notice (6) TLV-11 - unrecognized OID
Mon Jan 23 02:36:40 2012 68000200 Critical (3) DHCP FAILED - Request sent, No response
Mon Jan 23 02:36:34 2012 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received
Mon Jan 23 02:36:26 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jan 23 02:36:17 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Jan 23 02:35:47 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jan 23 02:35:33 2012 67040100 Error (4) DCC-ACK not received
Mon Jan 23 02:35:33 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jan 23 02:35:33 2012 67040100 Error (4) DCC-ACK not received
Mon Jan 23 02:35:29 2012 67021600 Error (4) DCC rejected parameter invalid for context
Mon Jan 23 02:33:12 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jan 23 02:03:58 2012 83010101 Error (4) Service Add aborted - No RSP
Mon Jan 23 02:02:42 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Jan 23 01:21:15 2012 73040100 Notice (6) TLV-11 - unrecognized OID
Mon Jan 23 01:20:48 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Jan 23 01:20:18 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jan 22 11:19:15 2012 73040100 Notice (6) TLV-11 - unrecognized OID
Sun Jan 22 11:18:53 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Jan 22 11:18:23 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jan 22 11:17:58 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Jan 22 11:17:28 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jan 22 11:14:44 2012 73040100 Notice (6) TLV-11 - unrecognized OID
Sun Jan 22 11:14:20 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Sun Jan 22 11:14:13 2012 73000200 Critical (3) REG RSP not received
Sun Jan 22 11:14:12 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jan 22 11:14:10 2012 73000200 Critical (3) REG RSP not received
Sun Jan 22 11:14:09 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jan 22 11:14:07 2012 73000200 Critical (3) REG RSP not received
Sun Jan 22 11:14:06 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Jan 22 11:14:04 2012 73000200 Critical (3) REG RSP not received
Sun Jan 22 11:14:03 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...

Not only is it full of errors from today only, but the clock time is way off! Is this a network issue or is my modem striving to be replaced?

reply to JeffMD
Neither...stop looking at logs and trying to self diagnose and get with me AFTER you have tested your wired connection please

reply to JeffMD
warcraft/desktop is wired. I know its hard to tell WHATS the problem with the logs... but usually the logs are quiet when everything is green, and crappy when somethings going on. esp when the modem reboots itself.

reply to JeffMD
You mentioned nothing about the modem rebooting itself in your last post but nonetheless in the meantime for the next two days remove your Netgear router and run straight to the modem please. Lets see how it runs that way. Everything else is fine.