Traffic Shaping on Teamspeak Ports ?

[quint]

Hello

last few weeks having a lot of problems with teamspeak, sound break up on both received voice and people complaining of break up from my end. Had this particular teamspeak for over a year on the same ip / port without problem and is used regularly by a bunch of friends.

I'm in nottingham

A friend whos on Virgin in Bristol is having identical issues, other people that share the Teamspeak on BT and various ADSL dont have the same issue.

Are Virgin now applying traffic shaping against Teamspeak ports, this particular teamspeak is on port 8823 & is there anything i can do about this , its very frustrating and kind of ruins the experience.

I do seem to get a number of timeouts and packet loss, as mentioned above friends not on Virgin are not getting the same issue which leads me to believe its not a problem at gameservers end.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

ping ts52.gameservers.com

Pinging ts52.gameservers.com [66.55.131.14] with 32 bytes of data:

Reply from 66.55.131.14: bytes=32 time=113ms TTL=49

Ping statistics for 66.55.131.14:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 113ms, Average = 113ms
Control-C
^C
ping -t ts52.gameservers.com

Pinging ts52.gameservers.com [66.55.131.14] with 32 bytes of data:

Request timed out.
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=126ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=102ms TTL=49
Request timed out.
Reply from 66.55.131.14: bytes=32 time=106ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=101ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=107ms TTL=49
Reply from 66.55.131.14: bytes=32 time=103ms TTL=49
Reply from 66.55.131.14: bytes=32 time=94ms TTL=49
Reply from 66.55.131.14: bytes=32 time=94ms TTL=49

Ping statistics for 66.55.131.14:
Packets: Sent = 17, Received = 15, Lost = 2 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 126ms, Average = 99ms
Control-C
^C
tracert ts52.gameservers.com

Tracing route to ts52.gameservers.com [66.55.131.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 7 ms 38 ms 10.225.56.1
3 12 ms 8 ms 47 ms nott-t2cam1-b-v153.network.virginmedia.net [80.4
.47.25]
4 18 ms 27 ms 7 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
5 38 ms 30 ms 15 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
6 14 ms 11 ms 12 ms pop-bb-a-so-100-0.network.virginmedia.net [213.1
05.172.14]
7 19 ms 54 ms 19 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 19 ms 32 ms 51 ms xe-1-3-0.cr1.ams2.nl.nlayer.net [195.69.145.219]

9 28 ms 20 ms 21 ms xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
10 98 ms 93 ms 124 ms xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
11 100 ms 93 ms 112 ms tge2-4.ar1.ewr1.us.nlayer.net [69.31.95.182]
12 123 ms 104 ms 92 ms as20473.tge2-2-105.ar1.ewr1.us.nlayer.net [69.31
.95.198]
13 96 ms 106 ms 94 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46]
14 95 ms 105 ms 118 ms 66.55.131.14.choopa.net [66.55.131.14]

Trace complete.

tracert ts52.gameservers.com

Tracing route to ts52.gameservers.com [66.55.131.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 9 ms 6 ms 10.225.56.1
3 15 ms 24 ms 10 ms nott-t2cam1-b-v153.network.virginmedia.net [80.4
.47.25]
4 8 ms 7 ms 20 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
5 12 ms 42 ms 14 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
6 12 ms 23 ms 13 ms pop-bb-a-so-100-0.network.virginmedia.net [213.1
05.172.14]
7 20 ms 22 ms 24 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 24 ms 28 ms 30 ms xe-1-3-0.cr1.ams2.nl.nlayer.net [195.69.145.219]

9 23 ms 22 ms 22 ms xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
10 92 ms 101 ms 112 ms xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
11 93 ms 94 ms 95 ms tge2-4.ar1.ewr1.us.nlayer.net [69.31.95.182]
12 144 ms 92 ms 93 ms as20473.tge2-2-105.ar1.ewr1.us.nlayer.net [69.31
.95.198]
13 122 ms 94 ms 104 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46]
14 119 ms 98 ms 96 ms 66.55.131.14.choopa.net [66.55.131.14]

Trace complete.




ping -t www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:

Reply from 212.58.253.67: bytes=32 time=16ms TTL=117
Reply from 212.58.253.67: bytes=32 time=19ms TTL=117
Reply from 212.58.253.67: bytes=32 time=24ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=16ms TTL=117
Reply from 212.58.253.67: bytes=32 time=24ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=42ms TTL=117
Reply from 212.58.253.67: bytes=32 time=20ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=23ms TTL=117

Ping statistics for 212.58.253.67:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 42ms, Average = 20ms
Control-C

WinXp 32
8800GT, Core2 Quad Q6600, 4 gig DDR3
Netgear WGT624 connected via cat5 / ethernet

Tried various router resets, connecting directly to modem, resetting mac address etc

Gaming and surfing seems reasonably normal , teamspeak poor even if only app running, dont believe its an application issue ..

have not tried contacting support yet, are the frontline able to deal with this kind of request and whats the best way to get the additional info to them ?

[Sirius]

We run our own Teamspeak server as part of the NTHWclan.co.uk gaming servers, We don't seem to be traffic shaped at all, The system is very good, Clear and does not drop out at all. In fact i am certain that VM dont traffic shape teamspeak.

We have had over 10 on teamspeak and 16 on the gaming server at the same time with no problems, Nearly all of us use VM

[MovedGoalPosts]

If you are being traffic shaped, it affects all traffic, not individual ports.

It's worth looking at other settings. The codec being used by Teamspeak? Did you have anything else running at the time you thought you had shut down, like torrents (my favourite trick)? Any recent changes to your sound or other drivers?

[Graham M]

Also your ping won't be using the teamspeak ports...

[Fatec]

Issues between team speak and VM connections is quite well known, its down to poor peer routing (and link ups), level3 is always over utilized as well, i think you are going to have to just put up with it (or try to get VM to sort something out, which i doubt will happen.)

VM have poor routing to practically everywhere these days (even giganews!)

[Zhadnost]

I dunno, I seem to get a pretty solid connection to everything I use, even when it's not located in docklands.

[Robertus]

Issues between team speak and VM connections is quite well known, its down to poor peer routing (and link ups), level3 is always over utilized as well, i think you are going to have to just put up with it (or try to get VM to sort something out, which i doubt will happen.)

VM have poor routing to practically everywhere these days (even giganews!)


So well known the none of me or my friends have experienced it?


:D

[CrowmanUK]

You could always give Ventrillo a go and see if you have any problems with that, it doesnt sort out the TS problems but it might be a way around it.

Edit: Which game are you playing when you get the problems? I had a pile of problems playing GRAW and using TS at the same time, turned out to be my fault in the end, I'd got the game on ultra sound quality and it was using all the resources on the soundcard leaving nothing left for TS, try using TS while no game is running and see if you still get problems too.

[quint]

Getting the problems without playing games, its just general drop outs as though the connection timesout for a moment or two , and although TS wont use the ICMP ports, i am still seeing regular loss and timeouts via that method which is also about the frequency of drop outs listening / speaking to people on TS.

So i dont believe its a resource or PC problem , particularly as its not just me and i have a bang upto date and well maintained system.

Unfortunately the TS is rented for another 6 months, but bearing in mind we've rented from gameservers for nearly 3 years without issue until recently and despite the occasional satelite delay, its not been an issue with it being housed in the states, the latency isnt really that much of an issue with TS. I might see if Gameservers will move us to another location with us being long term customers.

Ventrillo isnt really an option due to us still having a fair few months left and that 7 out of 10 regular users on TS via various ADSL dont have an issue, 2 of us on virgin do, just waiting to see if the other fella on Virgin is also getting similar probs

[Kymmy]

Looks like the gameservers TS is located in the states from the ping... I used to have major problems using TS when I was a ut99 sniper captain especially on gameserver IP's, nothing to do with VM as I was on ADSL at the time and more lkely to be a server issue than a port issue.

Try some other clans with public TS servers and see if the problem still exists.

[quint]

only people having issues on this teamspeak are both on Virgin Cable, adsl users are absolutely fine

The TS has been absolutely fine for years, in game and out.

[Nilrem]

That doesn't really mean much, it can be down to a problem with the routing from virgin to the host, or the routing after virgin, that because another isp connects at a different location is missed.

I'm using voice comms of various types on a regular basis with no problems.

A quick play with a trace routing programme* shows me that the connection to the op's server appears to be fine.
Right up to the last hop, where it's losing about 10% of the ping packets (which if it's happening to voice comms i'm guessing will cause a problem).


Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 192.168.1.1 1 2ms 1ms 0% 78 / 78 0ms / 19ms
* Unknown Host * 10.136.xxx.x 2 9ms 100% 0 / 77
xxxx-xxxxx-a-v124.network.virginmedia.n80.4.xxx.xx 3 8ms 27ms 0% 77 / 77 8ms / 119ms
lutn-t3core-1a-ge-013-0.network.virginme62.252.64.93 4 9ms 25ms 0% 77 / 77 7ms / 168ms
pop-bb-a-so-220-0.network.virginmedia.ne213.105.175.149 5 11ms 24ms 0% 77 / 77 9ms / 107ms
* Unknown Host * 195.50.91.69 6 12ms 22ms 0% 77 / 77 8ms / 158ms
ae-32-56.ebr2.London1.Level3.net 4.68.116.190 7 75ms 28ms 0% 77 / 77 13ms / 130ms
ae-44.ebr1.NewYork1.Level3.net 4.69.137.78 8 95ms 99ms 0% 77 / 77 85ms / 208ms
ae-2.ebr1.Newark1.Level3.net 4.69.132.98 9 101ms 114ms 0% 77 / 77 83ms / 198ms
ae-11-51.car1.Newark1.Level3.net 4.68.99.5 10 92ms 111ms 0% 77 / 77 81ms / 264ms
CHOOPA-LLC.car1.Newark1.Level3.net 4.79.189.182 11 92ms 118ms 0% 77 / 77 86ms / 352ms
66.55.131.14.choopa.net 66.55.131.14 12 86ms 100ms 9% 70 / 77 84ms / 194ms




*UO Trace - it's meant to be for checking the games servers, but it works, is easy to use (for any server) and free :p

[CrowmanUK]

Is it messing up all the time or just at certain times of the day? Just wondering if traffic management is rearing its ugly head and messing it up for you.

[quint]

thanks i'll try that additional trace and see what gameservers can do

i think its only evenings to be honest crowman, but it may be i've only really used it evenings since the problems began

am going to try and get a few on this weekend one afternoon and see how it fares if still having problems

[Fatec]

That doesn't really mean much, it can be down to a problem with the routing from virgin to the host, or the routing after virgin, that because another isp connects at a different location is missed.

I'm using voice comms of various types on a regular basis with no problems.

A quick play with a trace routing programme* shows me that the connection to the op's server appears to be fine.
Right up to the last hop, where it's losing about 10% of the ping packets (which if it's happening to voice comms i'm guessing will cause a problem).


Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 192.168.1.1 1 2ms 1ms 0% 78 / 78 0ms / 19ms
* Unknown Host * 10.136.xxx.x 2 9ms 100% 0 / 77
xxxx-xxxxx-a-v124.network.virginmedia.n80.4.xxx.xx 3 8ms 27ms 0% 77 / 77 8ms / 119ms
lutn-t3core-1a-ge-013-0.network.virginme62.252.64.93 4 9ms 25ms 0% 77 / 77 7ms / 168ms
pop-bb-a-so-220-0.network.virginmedia.ne213.105.175.149 5 11ms 24ms 0% 77 / 77 9ms / 107ms
* Unknown Host * 195.50.91.69 6 12ms 22ms 0% 77 / 77 8ms / 158ms
ae-32-56.ebr2.London1.Level3.net 4.68.116.190 7 75ms 28ms 0% 77 / 77 13ms / 130ms
ae-44.ebr1.NewYork1.Level3.net 4.69.137.78 8 95ms 99ms 0% 77 / 77 85ms / 208ms
ae-2.ebr1.Newark1.Level3.net 4.69.132.98 9 101ms 114ms 0% 77 / 77 83ms / 198ms
ae-11-51.car1.Newark1.Level3.net 4.68.99.5 10 92ms 111ms 0% 77 / 77 81ms / 264ms
CHOOPA-LLC.car1.Newark1.Level3.net 4.79.189.182 11 92ms 118ms 0% 77 / 77 86ms / 352ms
66.55.131.14.choopa.net 66.55.131.14 12 86ms 100ms 9% 70 / 77 84ms / 194ms




*UO Trace - it's meant to be for checking the games servers, but it works, is easy to use (for any server) and free :p

As i have said, is down to poor peer routing within VM itself and it aint going to get better (VM aint gonna fix it, either you have the problem or you dont)