High pings to Draytek 2910G

[Robert]

Here's the story:

About 2 months ago I started having issues with TF2. Now I had never noticed any other issues.

On Sunday evening whilst playing Gary's Mod I noticed my ping on ventrilo was around 1000ms+. I alt tabbed and it looked like this:

Quote:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=54ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=83ms TTL=255
Reply from 192.168.0.1: bytes=32 time=39ms TTL=255
Reply from 192.168.0.1: bytes=32 time=119ms TTL=255
Reply from 192.168.0.1: bytes=32 time=43ms TTL=255
Reply from 192.168.0.1: bytes=32 time=90ms TTL=255
Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
Reply from 192.168.0.1: bytes=32 time=80ms TTL=255
Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
Reply from 192.168.0.1: bytes=32 time=150ms TTL=255
Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
Reply from 192.168.0.1: bytes=32 time=168ms TTL=255
Reply from 192.168.0.1: bytes=32 time=11ms TTL=255
Reply from 192.168.0.1: bytes=32 time=196ms TTL=255
Reply from 192.168.0.1: bytes=32 time=32ms TTL=255
Reply from 192.168.0.1: bytes=32 time=201ms TTL=255
Reply from 192.168.0.1: bytes=32 time=98ms TTL=255
Request timed out.
Anyway - I quit the game and all was fine. I loaded up wow - no issues.

I've upgraded the firmware on my router to no avail. I connected directly to the internet which seemed to fix it. I then reset my firmware to manufacturer defaults. It seemed fine, but since then it has come back. I've also pinged the router from another PC whilst my PC is getting high latency and it's the same. I'm guessing that this rules out the wire as a problem.

Also I can max out my 20mb/s connection and have no issues. Anyway - not sure what to do next. I've used Wireshark and have some results but I'm not sure if I should post that as it has my IP - although I'm guessing it wouldn't be that hard for people to get it.

[Splash]

What other traffic do you have going through that router? I assume your PC is connected direct to the router?

[Robert]

Yes. Well the issue has happened with 1 or 2 computers active on the LAN.

It happens with just mine active (no other traffic apart from my PC)
Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 Nemesis:0 LISTENING
TCP 0.0.0.0:445 Nemesis:0 LISTENING
TCP 0.0.0.0:1110 Nemesis:0 LISTENING
TCP 0.0.0.0:2869 Nemesis:0 LISTENING
TCP 0.0.0.0:5357 Nemesis:0 LISTENING
TCP 0.0.0.0:19780 Nemesis:0 LISTENING
TCP 0.0.0.0:49152 Nemesis:0 LISTENING
TCP 0.0.0.0:49153 Nemesis:0 LISTENING
TCP 0.0.0.0:49154 Nemesis:0 LISTENING
TCP 0.0.0.0:49155 Nemesis:0 LISTENING
TCP 0.0.0.0:49159 Nemesis:0 LISTENING
TCP 127.0.0.1:1110 Nemesis:56284 ESTABLISHED
TCP 127.0.0.1:1110 Nemesis:56315 ESTABLISHED
TCP 127.0.0.1:1110 Nemesis:57091 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57100 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57109 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57114 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57118 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57121 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57124 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57125 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57134 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57137 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57170 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57173 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57200 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57218 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57265 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57299 TIME_WAIT
TCP 127.0.0.1:1110 Nemesis:57356 TIME_WAIT
TCP 127.0.0.1:52427 Nemesis:52428 ESTABLISHED
TCP 127.0.0.1:52428 Nemesis:52427 ESTABLISHED
TCP 127.0.0.1:52429 Nemesis:52430 ESTABLISHED
TCP 127.0.0.1:52430 Nemesis:52429 ESTABLISHED
TCP 127.0.0.1:56284 Nemesis:nfsd-status ESTABLISHED
TCP 127.0.0.1:56310 Nemesis:56311 ESTABLISHED
TCP 127.0.0.1:56311 Nemesis:56310 ESTABLISHED
TCP 127.0.0.1:56312 Nemesis:56313 ESTABLISHED
TCP 127.0.0.1:56313 Nemesis:56312 ESTABLISHED
TCP 127.0.0.1:56315 Nemesis:nfsd-status ESTABLISHED
TCP 127.0.0.1:57140 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57143 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57146 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57149 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57152 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57155 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57158 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57161 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57163 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57167 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57176 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57178 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57182 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57185 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57188 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57191 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57193 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57197 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57203 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57206 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57209 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57212 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57215 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57221 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57224 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57227 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57230 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57233 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57236 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57237 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57239 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57245 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57248 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57251 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57254 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57257 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57259 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57262 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57269 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57272 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57275 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57278 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57281 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57284 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57287 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57290 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57293 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57296 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57302 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57305 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57307 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57309 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57313 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57317 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57319 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57322 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57325 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57329 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57332 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57335 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57338 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57340 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57344 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57346 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57350 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57352 Nemesis:nfsd-status TIME_WAIT
TCP 127.0.0.1:57359 Nemesis:nfsd-status TIME_WAIT
TCP 192.168.1.10:139 Nemesis:0 LISTENING
TCP 192.168.1.10:51257 78.129.199.238:14363 ESTABLISHED
TCP 192.168.1.10:51365 by1msg3245820:msnp ESTABLISHED
TCP 192.168.1.10:56288 www:http ESTABLISHED
TCP 192.168.1.10:56319 text:nntp ESTABLISHED
TCP [::]:135 Nemesis:0 LISTENING
TCP [::]:445 Nemesis:0 LISTENING
TCP [::]:1110 Nemesis:0 LISTENING
TCP [::]:2869 Nemesis:0 LISTENING
TCP [::]:5357 Nemesis:0 LISTENING
TCP [::]:19780 Nemesis:0 LISTENING
TCP [::]:49152 Nemesis:0 LISTENING
TCP [::]:49153 Nemesis:0 LISTENING
TCP [::]:49154 Nemesis:0 LISTENING
TCP [::]:49155 Nemesis:0 LISTENING
TCP [::]:49159 Nemesis:0 LISTENING
TCP [2001:0:d5c7:a2ca:e3:7827:af3d:5585]:56327 [2001:0:d5c7:a2ca:302c:2d1a
:b1df:3b74]:49245 ESTABLISHED
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3544 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:50076 *:*
UDP 0.0.0.0:51814 *:*
UDP 0.0.0.0:63234 *:*
UDP 0.0.0.0:63235 *:*
UDP 0.0.0.0:64606 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49345 *:*
UDP 127.0.0.1:49346 *:*
UDP 127.0.0.1:54569 *:*
UDP 127.0.0.1:62743 *:*
UDP 127.0.0.1:62978 *:*
UDP 192.168.1.10:9 *:*
UDP 192.168.1.10:137 *:*
UDP 192.168.1.10:138 *:*
UDP 192.168.1.10:1900 *:*
UDP 192.168.1.10:54551 *:*
UDP 192.168.1.10:54568 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:5355 *:*
UDP [::]:64607 *:*
UDP [::1]:1900 *:*
UDP [::1]:54566 *:*
UDP [fe80::e3:7827:af3d:5585&#37;9]:1900 *:*
UDP [fe80::e3:7827:af3d:5585%9]:54567 *:*
UDP [fe80::20cc:8998:81a1:dab3%8]:1900 *:*
UDP [fe80::20cc:8998:81a1:dab3%8]:54565 *:*

[gss03]

The 2910 has a CPU usage thingy on it. It might show CPU spikes....

[Agent]

Do a master reset on it.

Does it do the same from other machines? Remember, the delay could be at the host.

[Robert]

It does the same on both machines e.g. if I launch steam on my PC and my PC starts to lag (lost packets/high pings to the router) then the other PC will.

I've already tried a master reset

CPU usage looks fine.

[TiG]

Robert are you running one of the Linux within Windows software systems?.

TiG

[Robert]

No mate