TeamSpeak Packet Loss

NachT

NachT

NachT

Associate
Joined
20 May 2006
Posts
1,068
Hey guys,

I'm hoping someone here will be able to help or provide some information towards this problem. I haven't been able to find anything on google which relates to this!

When I use TeamSpeak3, no matter what server I connect to - I get a high amount of inbound packet loss (about 20 - 70%). This causes problems in hearing anyone who tries to talk - makes more than half the convo sound like a bunch of Transformers!.

We also get the exact same problem when using TS3 on my mates laptop. So it's not the PC. We also tried joining a Mumble server, and Vent, and got the same issue. no one else on the server gets this problem.

I checked my internet connection, and upped my noise margin from 2.5db to 9db - however this made no difference.
Using pingtest.org and pining google.com repeatedly has no packet loss at all.

I did notice something though, but I don't know what could cause this. When we shut down the laptop, so only my PC was on on the network, the fault was gone on my PC.

The laptop was using wireless, and my PC is wired.

Any information would be great, or things to try ^^

Cheers guys
 
Have you configured any QoS on your router? Also do you have QoS packet scheduler enabled on your NIC?

Audio streams should transmit with a higher QoS value than bog standard data streams.
If ping is working fine without loss for say a 100 repeat count then it's likely something is competing for bandwidth with Teamspeak and winning at times. With QoS working then the audio stream should always win first dibs on any available bandwidth.
 
I can't seem to find any QoS related settings in my router config (DG834N with custom DGTeam FW).

I do have QoS packet scheduler enabled on my NIC.

And yeah, ping is fine to the server;

21807629.jpg
 
Don't fixate on Ping, it doesnt really tell you anything about packet loss it's only designed to measure latency. If a packet arrives more than 2 seconds late then it reports it lost, when it isn't, it arrived ok, it's just suffering high latency.

What that image shows is that the packet loss is only inbound, which means it's not likely to be QoS at your end causing it. As QoS only applies to the re-transmission of packets because you have no control over the order in which they're sent to you, you can only manage the order in which you send them out. Seeing as all your packets seem to be reaching the server then indications are that QoS side of things is working.

Do you have wireshark or any other packet dissection tool? Would be worth seeing if the inbound IP TOS value is being tweaked. It's possible your ISP or something on the way doing some sort fo traffic shaping is performing Diffserv replacement and bumping the QoS priority down.

Another thing to try is run wireshark while downloading a file via HTTP or FTP. IT should be possible to tell from the TCP protocol headers if packets are being lost and re-transmitted. Ping packets are tiny so are less prone to the effects of traffic shaping measures etc
 
Temporarily disable the router's 'SPI Firewall' via the web interface and confirm whether two clients can simultaneously achieve a decent connection quality. If so, and you want to keep the firewall on, then look at increasing the 'UDP Flood' limits.
 
ncjok said:
Temporarily disable the router's 'SPI Firewall' via the web interface and confirm whether two clients can simultaneously achieve a decent connection quality. If so, and you want to keep the firewall on, then look at increasing the 'UDP Flood' limits.
Click to expand...

This was it :)

The packets where falsely being blocked for a flood attack. Switching this off fixed the packet loss problem. My inbound packet loss doesn't go higher than 2% now - and I can hear everyone perfectly!

Thanks guys for all your input, much appreciated :)
 
You must log in or register to reply here.
Back
Top Bottom