New Teamspeak 3 server

[Firejack]

Lex has setup a new Teamspeak 3 server for the Community!

Download Teamspeak 3 from: http://www.teamspeak.com/
Server address = voice.terranovagaming.com
Password = Same as old Mumble server.(ask another Community member if you don't remember)

Get setup and come say hello!

Thanks again to Lex!

[frikin]

whats the pass word

[Caldazar]

I have send the pass by pm

[Firejack]

Server has high pings and packet loss for about half the people on the server. Any ideas Lex?

[Lex]

Yes, i dont know if you peeps seen the news, but the facebook party in Haren (Holland) is in my town... the local news channel (rtvnoord.nl) is using al lot of resources and might be responsible for my hickups.. i`ll see what i can do

[Firejack]

Pretty funny a party is causing this



Not sure if we'll need it but...

Scan.co.uk Backup Teamspeak server: 85.236.100.27:28137 (no password)

[Lex]

it should be functioning again tho, cant detect packetloss anymore and load seems to go down, eventho, i dont think anyone was prepared for this to happen

i can tell you its insane here in this village, but my car and house are still safe

[Firejack]

Server 30/32 right now. Busy

[Firejack]

Lex you any objections to me setting up Battlefield Squad VoIP on the new Teamspeak server? I'll need the Scan procon server whitelisting + Server Queries enabling.

Been trying to get this added to the Scan servers FOREVER but multiplay seem unable to accommodate our requests.

It'll only be for TNGC folks + maybe a few of the Scan guys to show them how it works. Then maybe get them to get another TS server away from Multiplay.

[Lex]

Go ahead. Do you have documentation or a a steplist for me what i need to change? If yes poke me. I`ll try to keep a better eye on the forums, but i was living in datacenter this week

[Firejack]

I had a quick poke around myself and most things seem to work. I'll set it up when the BF3 servers are empty. It shuffles around squads so don't want to do that while the server is full!

[Lex]

all is fine by me, if you do need to get in touch more quickly you can mail me

[Firejack]

Packet loss again tonight. Mostly UK peeps. I'm by far the worst with 9%

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Andrew>tracert 91.194.224.22

Tracing route to alex.osso.nl [91.194.224.22]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    18 ms    19 ms    17 ms  10.1.3.245
  4     *       24 ms    23 ms  10.1.2.169
  5     *        *        *     Request timed out.
  6    24 ms    23 ms   145 ms  XE5-0-8-0-GRTLONTL1.red.telefonica-wholesale.net
 [84.16.6.189]
  7    37 ms    36 ms    36 ms  te0-2-0-5.ccr21.lon01.atlas.cogentco.com [130.11
7.14.205]
  8     *       45 ms    44 ms  te0-0-0-4.mpd21.lon13.atlas.cogentco.com [154.54
.57.102]
  9    44 ms    43 ms    44 ms  te0-1-0-0.mpd21.ams03.atlas.cogentco.com [130.11
7.1.117]
 10    43 ms    44 ms    44 ms  te7-7.ccr01.ams04.atlas.cogentco.com [130.117.50
.226]
 11    45 ms     *       44 ms  149.6.129.163
 12    47 ms     *       47 ms  rtr-5-relined.rtr-3-rh.cj2.nl [46.182.218.1]
 13    47 ms    46 ms    46 ms  46.182.216.218
 14    47 ms     *       47 ms  p2p.cr1.tcn.osso.nl [217.21.194.33]
 15    48 ms    47 ms    47 ms  alex.osso.nl [91.194.224.22]

Trace complete.

C:\Users\Andrew>

Code: Select all

C:\Users\Andrew>ping -n 25 91.194.224.22

Pinging 91.194.224.22 with 32 bytes of data:
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=48ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=46ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=49ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Request timed out.
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48
Reply from 91.194.224.22: bytes=32 time=47ms TTL=48

Ping statistics for 91.194.224.22:
    Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 49ms, Average = 47ms

C:\Users\Andrew>

The 10.1.x addresses are adaptive firewalls.

Somes long a lot of tops for UK to Holland. Must be crappy routing

[blitzkrieg]

We need a larger server. And for the time being if there are a lot of people online don't use the AFK channel if you're not playing/using the TS please vacate your self.

[Dismus]

Packet loss again tonight. Mostly UK peeps. I'm by far the worst with 9%

Code: Select all

C:\Users\Andrew>tracert 91.194.224.22
:snip
  4     *       24 ms    23 ms  10.1.2.169

That shows packets being dropped between hops 3 and 4. Give your firewall a kick.