dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
893
share rss forum feed

silverforte

join:2012-05-26
Kannapolis, NC
Reviews:
·Time Warner Cable

Latency issues again

I've posted here in the past and cooperated with a rep to get my problem solved, so I'm hoping I can get that experience again. Last time, I was having spikes of latency issues where my ping would go from 75 to 200-500 whenever anyone was doing more than one thing at any time on our internet connection, even if it was from a single computer. Now, I'm having a similar issue but not quite as bad as before. Right now, I stay at a steady 80-100 ms and it really feels like more, as if it's not as stable as it should be and I'm actually getting internet in small, rapid bursts instead of a constant connection. It's really bothersome and clearly something is up again. Modems fine, didn't start happening til about two weeks ago. Figured I'd give it time to subside, it hasn't.

So, here we are again, same situation as before even if it isn't as severe. It's irritating because I'll be doing something like playing a game and, at different points, my connection will just stop for like two or three seconds then resume. I'll check my latency and it'll be higher than it was before and this just repeats over and over.

North Carolina, Concord area.

Edit/update.

Just loaded up a game, seeing 800 ms latency...

silverforte

join:2012-05-26
Kannapolis, NC
Reviews:
·Time Warner Cable

2 edits
Anyone? I'm to the point where I can't really do much and it's the third time, so I'm completely ready to be done with this issue.

Update - Can't do anything, at all.

»i10.photobucket.com/albums/a146/ ··· 329c.png

That's an image of my latency right now. Steady at 1400+. Nobody is doing anything. Even tested resetting the modem, using cmd to ipconfig /release and /renew, I tried changing the modem settings to disable wireless, I changed the ID of the modem and the security key just in case someone was messing with me. Nothing, no change. I noticed in the modem log some weird stuff like this -

Date/Time Facility Severity Message
Mar 12 17:39:05 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:39:05 user info kernel: br0: topology change detected, propagating
Mar 12 17:39:05 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:39:05 user info kernel: br0: topology change detected, propagating
Mar 12 17:39:05 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:41:06 user alert kernel: Intrusion -> IN=atm0 OUT= MAC=2c:e4:12:45:d2:59:00:12:43:42:41:40:08:00 SRC=173.88.29.253 DST=166.82.23.209 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=14796 DF PROTO=TCP SPT=54599 DPT=6882 WINDOW=8192 RES=0x00 SYN
Mar 12 17:41:32 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:32 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:41:32 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:32 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:32 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:32 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:32 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:41:32 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:32 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:41:32 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:32 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:32 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:32 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:41:33 user info kernel: device wl0 left promiscuous mode
Mar 12 17:41:33 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:34 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:41:34 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:34 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:34 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:34 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:34 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:41:34 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:34 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:41:34 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:34 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:34 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:34 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:41:35 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:38 user info kernel: device wl0 left promiscuous mode
Mar 12 17:41:38 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:38 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:41:38 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:41:38 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:41:38 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:38 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:41:38 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:38 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:38 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:39 user info kernel: device wl0 left promiscuous mode
Mar 12 17:41:39 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:40 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:41:40 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:40 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:40 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:40 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:40 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:41:40 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:40 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:41:40 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:40 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:40 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:40 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:41:45 user info kernel: device wl0 left promiscuous mode
Mar 12 17:41:45 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:45 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:41:45 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:45 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:45 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:45 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:45 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:41:45 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:45 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:41:45 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:45 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:45 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:45 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:41:46 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:49 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:49 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:49 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:49 user info kernel: device wl0 left promiscuous mode
Mar 12 17:41:49 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:50 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:41:50 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:50 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:50 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:50 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:41:50 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:41:50 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:41:50 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:41:50 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:50 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:41:50 user info kernel: br0: topology change detected, propagating
Mar 12 17:41:50 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:43:11 user info kernel: device wl0 left promiscuous mode
Mar 12 17:43:11 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:11 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:43:11 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:11 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:11 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:11 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:11 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:43:11 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:11 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:43:11 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:11 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:11 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:11 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:43:13 user info kernel: device wl0 left promiscuous mode
Mar 12 17:43:13 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:13 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:43:13 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:13 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:13 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:13 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:13 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:43:13 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:13 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:43:13 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:13 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:13 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:13 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:43:15 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:18 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:18 user info kernel: device wl0 left promiscuous mode
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:18 user info kernel: device wl0 entered promiscuous mode
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:18 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering disabled state
Mar 12 17:43:18 user info kernel: br0: port 1(eth0) entering disabled state
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering learning state
Mar 12 17:43:18 user info kernel: br0: port 1(eth0) entering learning state
Mar 12 17:43:18 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:18 user info kernel: br0: port 2(wl0) entering forwarding state
Mar 12 17:43:18 user info kernel: br0: topology change detected, propagating
Mar 12 17:43:18 user info kernel: br0: port 1(eth0) entering forwarding state
Mar 12 17:54:01 user alert kernel: Intrusion -> IN=atm0 OUT= MAC=2c:e4:12:45:d2:59:00:12:43:42:41:40:08:00 SRC=76.115.58.93 DST=166.82.23.209 LEN=52 TOS=0x00 PREC=0x00 TTL=106 ID=19530 DF PROTO=TCP SPT=52544 DPT=6882 WINDOW=8192 RES=0x00 SYN
Mar 12 18:11:07 user alert kernel: Intrusion -> IN=atm0 OUT= MAC=2c:e4:12:45:d2:59:00:12:43:42:41:40:08:00 SRC=184.39.192.50 DST=166.82.23.209 LEN=48 TOS=0x00 PREC=0x00 TTL=106 ID=12035 PROTO=TCP SPT=58108 DPT=6882 WINDOW=8192 RES=0x00 SYN UR
Mar 12 18:30:13 syslog info -- MARK --
Mar 12 18:43:55 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:43:55 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:43:55 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:43:55 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:43:55 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:43:55 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:43:57 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:43:57 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:43:57 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:43:57 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:43:57 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:43:57 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:44:01 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:44:01 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:44:01 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:44:01 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:44:02 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:44:02 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:44:07 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:44:07 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:44:07 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:44:07 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M
Mar 12 18:44:08 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Mar 12 18:44:08 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:220".^M

I don't know much about the system log and the jargon in it but some of that looks strange to me. Maybe it'll be of help, I don't really know. Just willing to try anything at this point to get my internet back to acceptable standards.


Windstream
Premium,VIP
join:2009-03-31
Twinsburg, OH
kudos:38
We apologize for the issues you are experiencing. We will need your dsl phone number so we can look at the line, do some testing etc...We will also look and see if we are working on latency in the area.
Thanks,
Patricia
Support Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com

silverforte

join:2012-05-26
Kannapolis, NC
reply to silverforte
It's been several days and I'm not getting any updates. No response from PM. I was told it'd be a few days before I heard anything back but it's been five.


Windstream
Premium,VIP
join:2009-03-31
Twinsburg, OH
kudos:38
I have advised the agent you are working with that you would like a response. I apologize for the delay. Thank you for your patience and understanding as we are working with significant volume.

Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com

silverforte

join:2012-05-26
Kannapolis, NC
Thanks Aaron.