Networking issues

[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.

My router's a draytek 2910G. I first noticed an issue with TF2 about 2 months ago, but I hadn't noticed the issue with local ping at the time (everything else seemed to play fine so I just left it).

[LeperousDust]

Checked your lan drivers? Not running on the out of the box vista/xp ones?

[Dr. Z]

It looks like your router, tbh.

[Robert]

Yeah I'm hoping there's a setting or something which can help...

It isn't my NIC Alex as it happens on another machine.

[Burble]

What results do you get if you ping one machine from the other?

[Robert]

1ms...

C:\Users\Robert>tracert 192.168.0.11
Tracing route to DEREK [192.168.0.11]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DEREK [192.168.0.11]
Trace complete.
C:\Users\Robert>
Whilst playing TF2:

Ping statistics for 192.168.0.11:
Packets: Sent = 225, Received = 225, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 0ms
While playing I got loss and choke - yet the pings seemed ok.


I went back on to TF2 whilst pinging my router - had the same loss, but you can see the huge difference in ping (compared to when I pinged the other PC).

Request timed out.
Reply from 192.168.0.1: bytes=32 time=116ms TTL=255
Reply from 192.168.0.1: bytes=32 time=71ms TTL=255
Reply from 192.168.0.1: bytes=32 time=52ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=14ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time=152ms TTL=255
Reply from 192.168.0.1: bytes=32 time=27ms TTL=255
Reply from 192.168.0.1: bytes=32 time=234ms TTL=255
Reply from 192.168.0.1: bytes=32 time=55ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Request timed out.

Ping statistics for 192.168.0.1:
Packets: Sent = 547, Received = 545, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 234ms, Average = 1ms

[Wellington]

I went and played TF2 and got horrendous loss - but pings seemed OK?

Don't blame the ping for your papness.....

Sorry I'll go now as I have nothing constructive to say...

[Garp]

I've grabbed a look at the wireshark dump you gave me and I'm seeing a scary number of packets arriving corrupted. So either the wiring between you and it is corrupted, the router is corrupting packets, or your machine is corrupting packets.. take your pick :D

With the amount of failures its causing a large amount of repeated data to be thrown back and forth.

edit: Maybe.. http://www.wireshark.org/faq.html#q11.1

[Chuckles]

Sorry if I missed it, but are they wired to router or wifi?

[Robert]

It's wired - if my network card was corrupting packets would that have an adverse effect on the other PC?

Edit: I disabled TCP Checksum Offload (IPv4) and UDP Checksum Offload (IPv4) and most of the errors seem to have gone...

Not sure if that's because they aren't there or whether they just aren't being shown.

[LeperousDust]

I think it would because it would be making the router do more work, and they're be extra useless traffic being passed back and fourth.

[Robert]

Well went on TF2 and I had no loss...pings where fine. I'm not sure if it's because I have disabled them or what...

Gonna check my network speed incase it has had an effect.

With those settings off:

Ping statistics for 192.168.0.1:
Packets: Sent = 2623, Received = 2623, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms

Was playing for around 30 minutes.