This tutorial will explain how to setup and configure a DDoS protected Teamspeak 3 server. This guide assumes you know how to setup Teamspeak or already have a server running (and you have access to it)
Step 1: Backend Setup
Setup Teamspeak on your server, this server will be from here on referred to as the "backend server". On the backend server you may use whichever Operating System you are most familiar with, however if unsure we recommend Debian Linux.
Please ensure that the service is running and connectable on the backend server.
Step 2: Purchase DDoS Protection Service
Pick a suitable package from the DDoS protection page. We suggest choosing a product with a point of presence (PoP) closest to your backend server and it's users.
During the purchase process you will be asked to:
- Name your service (important if you plan to have many services)
- Select the filtering location & tier (choose a location close to your backend server). If in doubt we recommend the Standard Anycast product tier.
- Select the amount of Clean Bandwidth required to run your service (not attack traffic)
Step 3: Encapsulation Setup (Optional, but recommended)
This step is only required if you are intending to use a GRE, IP-in-IP or IPSec Tunnel. If you are intending to use a Reverse Proxy (RP) style connection (the easiest) then you can skip this step.
Teamspeak generally works best over a tunnel.
A Reverse Proxy only proxies connections to your backend and can be useful for servers that do not require to set bans on player IP addresses or do not have command line skills to set up a network interface (or when using a panel that does not give access to console).
An encapsulated backend requires support on the Backend Server, currently Windows and Linux Operating Systems are fully supported, with partial support for FreeBSD. Most Enterprise or even SOHO Routers also support GRE or IP-in-IP tunneling, if supported you may be able to configure the router to terminate the encapsulated network.
Encapsulated networks can be created from your services "Tunnels" page, the link for which can be found in its Action menu. To create a Tunnel you need to specify the backend servers IP address, as well as depending on the encapsulation type chosen security keys (GRE) or passphrases (IPSec PSK). If unsure as to the appropriate encapsulation type we recommend using GRE. Alternatively to the form in your dashboard you may also use the form below to create a tunnel, just input details for your backend server and select your service.
We provide scripts / software to install the encapsulated tunnel onto your backend server in the Dashboard. On your services Tunnels page you should see the list of tunnels which have been created. In the action menu for the tunnel there is a page titled "Setup Tunnel", here you can download the provided Linux setup script, or the Windows tunneling software with your configuration built-in.
For more information on GRE/IP-in-IP/IPSec Tunnels including installation instructions click here.
Step 4: Add Ports
Add the ports required to run your service. Teamspeak by default uses multiple ports 9987 (UDP) as the main server port. Additionally ServerQuery is listening on port 10011 (TCP) and file transfers will use port 30033 (TCP)
If unsure you can determine what port(s) the service bound to by using the
netstat commands as appropriate.
There is a form in the dashboard for creating ports, this can be found in your services action menu as the "Ports" page. To add a port click the "Add Port" button towards the bottom of the page. Then fill the created form with the values you can see below in the example / integrated form. Alternatively, you can also use the form below to create the port for your service, just configure the appropriate backend by either:
- Selecting the Encapsulated Type, and then the appropriate Tunnel (as created in Step 2); or
- Entering a Backend IP address for a Reverse Proxy style port.
Note: You can setup your backend Teamspeak server on a different port and forward port 9987 (UDP) from your IP with us. This is especially useful on shared IPs or hosts.
Step 5: Finish & Test
Once all steps are completed and the progress bar for deployment of the configuration reaches 100% you should be able to connect to your service on your Filtered IP.
This Filtered IP is the address that you should use in any DNS names, or supply to any connecting users. All traffic which arrives at configured ports on a Filtered IP will be filtered for attack, and then forwarded to your configured backend server.
Note: If you (or your network provider) run a firewall either ensure the Backend Communication address (unless otherwise specified, your filtered IP) is whitelisted or that the firewall is disabled.
May your audio be clear and un-interrupted.