If you’re a person like me, you may have also a problem with Flash based streams. Flash is and always has been a resource hungry monster with a lot of security issues. The problem is that a lot of streaming platforms still requiring Flash in order to let you watch their streamers, shows or programs. One of this streaming portals for e.g. is Twitch. But luckily there is a solution for a problem like this. The software Streamlink.
Streamlink is a fork from Livestreamer. The fork happened because the main developer of Livestreamer decided to drop the development for it. Since then, a lot of work has been made in Streamlink, including additional plugins for a lot of video on demand services or streaming platforms. Streamlink is written in Python and uses different libraries to allow users to watch video streams like Twitch with their favorite video viewers (like VLC, MPlayer and so on).
How to install Streamlink on Ubuntu
Steamlink can be easily installed under almost every Linux distrubution. On Ubuntu the latest and greatest Streamlink version can be downloaded through a so called PPA. A PPA is an addition to the already existing package repositories. This PPA is maintained by the official Streamlink developers and can be added to your system like this:
That’s it. With these three simple commands you’ve installed Streamlink under your Ubuntu box. There are several other Linux distrubtions supported and there are also Windows and OS X binaries which can be used. You see the full list of supported operating system on the official download page of Streamlink here: Streamlink installation.
How to use Streamlink?
Now that you’ve installed Streamlink, we can start using it. Just simply open a terminal window and enter streamlink, followed by the URL to the stream / video you want to open with your personal video player of your choice (the stream will be shown with the best possible quality, due to the option best):
user@machine:~$ streamlink https://www.twitch.tv/rocketbeanstv best
Platforms like Twitch and YouTube are already supported of course. But there are plenty of other TV stations and Video-on-demand platforms, which are supported and can be used with streamlink, including the Itlian TV station RAI or the german ARD channel. A complete list of built-in plugins can be found here: Streamlink built-in plugins
Tune your Streamlink
Streamlink has a configuration file which is located in your home directory as a hidden file under Linux machines. This file is called .streamlinkrc. You can basically set every option you can also pass to Streamlink through command line in the configuration file. A full set of available options is listed here: Streamlink options. An important option here however is to set the desired player you want to use with Streamlink. For e.g. if you set the following line in your .streamlinkrc, you are using VLC as the default player whenever you open a stream with Streamlink:
You can change vlc with mplayer any other video play of course. You can also add options which should be passed to the video player. For e.g. starting a stream in full screen with VLC:
Streamlink (or the former livestreamer) is a very needed and loved piece of software. It literally brings back the fun in watching live streams on Twitch or similar platforms. You don’t need to use flash in order to watch your favorite streams. Besides this, streamlink in combination with your video player of choice is way lesser resource hungry than the old flash technology. Give it a try. You will not regret it 😉 However, one downside: There will be no ads shown. While this sounds like a good thing in the first place, please keep in mind that the streamer you’re watching doesn’t get any money. So please, if you enjoy the stream you’re watching, consider subscribing to them for a few bucks per month. The incoming helps the streamer to go on with his / her work and helps Twitch to let the servers running in the future.
You can do a lot of things with SSH besides working securely remote on machines. I’ve already covered at another article how to tunnel (port forwarding) through SSH. This time we’re looking at a way to use SSH as a proxy.
SSH: A tool not only to do remote work
SSH (Secure Shell) is mostly used to do maintenance on your Linux machines. However, over the years the capabilities of SSH has been extended from a simple secure „remote maintenance protocol“ to a utility which is capable of doing things like X-Forwarding (for forwarding graphical application), port forwarding or providing a SOCKS proxy.
Why do you even want to use an proxy server?
Proxy servers are helpful in a lot of ways. For e.g. if you’re staying some nights in a hotel or you’re in any other public Wireless LAN which blocks a specific website you want to visit a proxy will help you to surpass the filter. Or if you are forced to use techniques like DSLight, were you have to share a single IPv4 address with other users. Or to unblock videos on Netflix which are blocked in your country. You see, the situations where a proxy server is helping you are almost countless. But why would you want to „setup“ an proxy server on your own? The simple answer is, that a lot of the public proxy servers are simply overloaded. They have to handle so much traffic that you sometime barely be able to get 50% of your normal internet speed while using one of these public proxy servers. Besides this, using SSH as a proxy is really easy.
How start a SOCKS proxy server by using SSH
In order to establish a SSH connection to your server which will then be an SOCKS proxy, you have to have the SSH server installed on the server side and the client software on the client side of course.
Using SSH as a proxy on Linux or Mac
For Linux or Mac you can use the SSH client command which is integrated in both systems. The following command would start an SSH connection, where your SOCKS proxy would then be locally reachable on port 19999 (19999 is just an suggestion and can be changed to almost everything starting from 1024 to 49151 (so called „user ports“)) :
user@client:~$ ssh -D 19999 user@server
After the connection has been successfully established, configure your browser to use the proxy server (follow the instructions below).
Using SSH as a proxy on Windows
Windows doesn’t comes with an SSH command integrated. This means we need an additional software in order to get connected and use the SSH server as a proxy. My recommendation here is PuTTY. PuTTY is a lightweight SSH client for Windows, which is the counterpart of the SSH command on Linux / Mac. You can download it here. After the download is finished, start PuTTY and enter the server you want to connect to like this:
Navigate to Connection –> SSH –> Tunnels and enter the port 19999 in the Source port field (19999 is just an suggestion and can be almost everything starting from 1024 to 49151 (so called „user ports“)). After you’ve entered the desired port number, ensure that you’ve selected Dynamic instead of Local:
Click on the button Add in order to tell PuTTY to actually use the given information for the next connection. If you clicked on Add, you should see the port number you have chosen with the letter D in the upper box. If you’ve done this as well, you’re ready to connect to your server. After the connection is successfully established, go on and configure your browser (follow the instructions below).
Configure Firefox / Google Chrome to use the SOCKS proxy
Now that we’ve connected successfully to our server via SSH, we can actually use the SOCKS proxy which has been provided with the actual SSH connection.
Configuring Firefox to use the SOCKS proxy
Click on the upper right options Symbol (represented as three horizontal lines) and click on Preferences. On the upcoming window, select General and scroll down until you see the context Network proxy. Click on Settings and enter your SOCKS proxy details like this:
Ensure that you’ve checked the box Use this proxy server for all protocols. After you’ve clicked on OK you’re ready to go. Use portals like BearsMyIp to check if you’re actually surfing through your SSH SOCKS proxy tunnel. Configuring Google Chrome (or Chromium) to use the SOCKS proxy For Googles Chrome browser you have to use the command line in order to set your SOCKS proxy. This includes Windows users as well. To start Googles Chrome using your SSH SOCKS proxy start the browser like this:
Of course you can change google-chrome to chromium if you’re an Chromium user instead.
An proxy server does have it’s advantages. However, public proxies are sometimes overloaded and you will recognize that as a significantly slow down of your internet connection when you start using them. As an alternative you can use SSH as a simple and fast way to make yourself an SOCKS proxy. Using SSH as a SOCKS proxy is a lot easier than configuring an Apache with Squid for e.g.. If you have a server and you need a proxy, I highly recommend you to use SSH in order to get a safe, fast and stable proxy server with a single command or a few clicks.
This article is about how to setup a TeamSpeak 3 server on your Linux box. Thanks to the TeamSpeak 3 developers, this process is rather easy and you should have a running TeamSpeak 3 server within minutes. TeamSpeak 3 is a heavily used solution (if not the most used one) to do low latency voice chat while gaming. For e.g. if you use Skype, the delay and the traffic between the talking people will be much higher, besides the Skype client being way more bloated than TeamSpeak. Besides TeamSpeak 3 there are other gaming based low latency solutions like Discord (which uses central servers without the possibility to setup your own instance) and Mumble.
The TeamSpeak 3 Server doesn’t really need any extra libraries in order to work. With a new Debian 9 setup for e.g. it start without any additional libraries. However to download and extract the server software we need some additional software, in this case a download manger (wget) and the utility to extract the compromised server software (bzip2). With the following command you will install this needed utilities. In this case we use Debian / Ubuntus package manager APT:
Now that all the needed utilities are on board, let’s move forward and install the server software itself.
Download and install the TeamSpeak 3 Server
TeamSpeak 3 is a proprietary software solution. Due to this fact you will not be able to install it from the repositories of your Linux distribution. So this means you have to download it from the developers homepage onto your server. You can download the latest TeamSpeak 3 Server software here. As of writing this tutorial the latest and greatest TeamSpeak 3 Server version was 22.214.171.124. Whenever you go through this tutorial, your version number may be a newer one. The following command downloads version 126.96.36.199 to your server:
After the download is finished (which can take some time depending on your network speed), we can extract the downloaded server software. The following command is doing this:
user@server:~$ tar xfvj teamspeak3-server_linux_amd64-188.8.131.52.tar.bz2
Now it’s time to start the server for the first time.
Starting the TeamSpeak 3 Server
Now, that we’ve downloaded and extracted the server software, we will be able to start the server software. To do so, we have to change into the TeamSpeak Server directory (which has been automatically created with extracting the server software) and issue the command to start the server:
user@server:~$ cd teamspeak3-server_linux_amd64
user@server:~/teamspeak3-server_linux_amd64$ ./ts3server_startscript.sh start
The first start takes some time, approximate 1-3 minutes. After the first start is finished, you will get an output like this:
I M P O R T A N T
Server Query Admin Account created
loginname= "serveradmin", password= "BVV2YUIJ"
I M P O R T A N T
ServerAdmin privilege key created, please use it to gain
serveradmin rights for your virtualserver. please
also check the doc/privilegekey_guide.txt for details.
Important: You should write down the server query admin account on a piece of paper, or you save these informations in a password database. This account is needed in emergency cases, like lost TeamSpeak user data or hacking attempts. In this case we only need the privilege key for now. Store the line, starting with token= in a text file. We need this token later on. To finally ensure if you’re server is running correctly, you can issue the following command:
user@server:~/teamspeak3-server_linux_amd64$ ./ts3server_startscript.sh status
Server is running
If the output Server is running is welcoming you, it’s time to connect to your new server.
Connect to your server and give yourself admin rights
At this point I assume, that you’ve already installed the TeamSpeak 3 client onto your computer. If you didn’t, you should download it here. If you’re a Linux user, you have to download the TeamSpeak 3 client through the link. You will not find the TeamSpeak 3 client in the distribution repositories due to the same reason as you will not find the TeamSpeak 3 server software. To connect to your server, start the TeamSpeak 3 client and click on Connections –> Connect or use the hotkey CTRL+S. In the upcoming dialog, enter the IP address or name of your server and pick a nickname which you want to use on that server and hit the Connect button.
The server recognizes that the server was initially setup and pops up another dialog where it asks for a so called Privilege Key. This Privilege Key is the generated token we’ve saved a few steps before in a text file. Open the text file (if not already) and copy everything after token= and insert this key into the dialog box like this:
After you’ve used the privilege key you can delete the text file. A privilege key is for onetime use only. However, you should now see a new symbol besides your nickname which states that you’re an Administrator. From now on, you should be able to create channels, server groups, edit the servers name and so on.
After this step your TeamSpeak 3 server is completely and fully setup. You can now close the SSH connection to your server and start to share your servers address with your friends and start talking 🙂
While the TeamSpeak 3 software is mainly rock solid, you should take care that your server is always up to date. To update the TeamSpeak 3 server software go to their official homepage, download the newest version (like you did before in this tutorial with wget) and extract it. The files will be overwritten besides the database files. This ensures that you don’t have to start all over again when you do an update. However, you have to stop the TeamSpeak 3 server before you update it. You can do this easily like this:
user@server:~$ cd teamspeak3-server_linux_amd64
user@server:~/teamspeak3-server_linux_amd64$ ./ts3server_startscript.sh stop
After you’ve extracted the updated server files you can start the server again:
Please be also aware that you should use a firewall or package filter solution like IPTables. A server with the latest security patches is good, but a firewall solution will always increases the security these days.
In times where almost everything goes more and more centralized (Discord, WhatsApp, …) I feel that a solution like TeamSpeak 3 is really needed. I know there are other solutions like Mumble which has the additional benefit of being Open Source, however, we can’t have enough decentralized solutions if you ask me 😉 I hope this tutorial is helpful for you. If you have any questions or if you just want to leave a feedback, use the comment section below.
A lot of people who are running a rented Linux (v)Server are interested in creating a Counter-Strike: Global Offensive server. Creating a CSGO server under Linux is rather easy, Valve really did their homework here. The following short tutorial will give you the needed instructions to create a Counter-Strike: Global Offensive Server under Debian, Ubuntu or openSUSE:
1. Create a new user
First of all, you should really create a new user in your Linux system. The reason for that is simple: security! If your main user, or even your root user, is running the CS:GO server and is hacked later on, the hacker maybe is in the position to get access to the system behind the Server. With that being said, he may be able to get full access to the shell and he may be able to manipulate the system. To create new account on your Debian, Ubuntu or openSUSE system, you have to enter the following commands:
So, the first commands creates a new user, called csgosrv. The seconds commands sets a new password for this user. The password you enter here will not be prompted. The third command creates a new directory called csgosrv under the directory /home. This will be the standard home directory for the user csgosrv we’ve created before. The fourth and last command sets the owner to the created user csgosrv and the group owner of the created csgosrv home directory to users.
2. Install needed dependencies
In this step we need to download the needed libraries in order to get the Steam command line tool working. If these libraries / tools are not installed, the Steam command line client (provided by Valve), will fail to start. If you’re on a 64-Bit Debian or Ubuntu system you have to enable the i386 architecture in the first place. This is needed because the server software is written for the 32-Bit architecture. If you’re on a 32-Bit Ubuntu or Debian, you can skip this command:
root@server:~# dpkg --add-architecture i386
The following two commands are needed for 32-Bit and 64-Bit systems. They will update the repository information and install the needed libraries:
If you’re on a openSUSE system, the commands are doing the same, but the syntax is different. The following two commands are updating the package repository and installs the needed libraries on a openSUSE system:
Now, that you have installed all the needed libraries, we can go on and start downloading and installing the server software.
3. Download Steam
Downloading the Steam command line tool is very easy. You can always get it directly from Valve. But before we start downloading the client, we should change to the beforehand created user csgosrv. We can do this with the following command:
root@server:~# su - csgosrv
As an alternative you could close your SSH session and reconnect with the user csgosrv. Now that we’re working with the right user, it’s time to download and extract Steam:
csgosrv@server:~$ mkdir steam
csgosrv@server:~/steam> cd steam
csgosrv@server:~/steam> wget http://media.steampowered.com/client/steamcmd_linux.tar.gz
csgosrv@server:~/steam> tar xfvz steamcmd_linux.tar.gz
So, the first two commands are creating a new directory, called steam, and directly changed into it with the help of the cd command. The third command is downloading the Steam CMD tool with the help of the tool wget. The fourth and last command extracts the so downloaded .tar.gz archive. After you’ve done this steps successfully you can go on and download the CS:GO server software.
4. Setup Steam and install CS:GO server files
This command will update the steam command line tool and installs the application „740“ which is the Counter-Strike: Global Offensive server. For now you don’t need to have your steam credentials ready. You can update steam and install the server software as an anonymous user:
This command will take some time and the so downloaded server software needs round about 15 GB hard disk space. The Server software will be installed in the directory /home/csgosrv/steam/csgo_server.
5. First start of the CS:GO server
Now that you have successfully downloaded and updated the Counter-Strike: Global Offensive server, we can do a test run. With the following command we can start the server with the mode Classic Casual and the Mapgroup mg_bomb which includes the old bomb spot maps like de_atztec or de_dust / de_dust2:
You will now get a lot of output. This is normal and shows you, that the software is working. However, at the end of all the lines you will find a message like this one:
* No Steam account token was specified. *
* Logging into anonymous game server account. *
* Connections will be restricted to LAN only. *
* To create a game server account go to *
* http://steamcommunity.com/dev/managegameservers *
Basically this message means that your server is not registered at Vale. As long as you don’t register your server at Vale, you will only be able to connect to the server via LAN, not via the internet. It will never be an official server played on. To make your server ready for the internet, you have to go on with the next step (you can terminate the actual running session with an CTRL+C combination).
6. Make your server an official registered one
To register your CS:GO server at Valve and make it ready for internet play, you have to register the server directly at Valve. To do so, visit the following link: Steam Server management. Login with your steam credentials (if you haven’t already) and enter the number 730 as the App ID in the first text box. The second text box can be filled with whatever you want. It’s just a comment field. For e.g. if you have more than one server you could write down the hostname here so that you can always directly see which token belongs to which server. Click on Create to get your Token: After you clicked on Create you will see your token for your server. The token can only be used on one server for one active session. You can’t use the token for multiple servers at the same time. You have to create a new token for each of your servers. Now that you have created your token, you can use it to start the server as an official CS:GO server with the following command:
Of course you have to replace the YOURTOKEN with the token you’ve created before. If there is no firewall blocking the traffic, you should now be able to find your server via the CS:GO server browser or connect directly via the hostname / IP to it.
7. Start the CS:GO server in the background
You may already noticed, that the CS:GO server stops running when you close the SSH connection. This is, because the CS:GO server software needs an active terminal / SSH session to go on running. However, there is a tool which is called screen. If you’ve followed this tutorial, you already have installed screen at the first steps. The following commands starts the CS:GO server in the background with the help of screen.
As long as you are connected (attached) to the screen session, you can do anything here like in a normal terminal session. If you want to leave the screen session again, just press CTRL+a, followed by the key d (CTRL+a sends a signal to the screen program that the next key stroke is something screen has to handle. The d key says to screen than: detach!).
If you have problems connecting to your server, you should check if there is no firewall blocking the traffic. If there is any firewall doing so, you have to unlock the port 27015 (UDP) for your server. For a more further configuration of the server (settings like warm up, max player count, map rotation and so on) you should visit the following page. It contains a almost complete server.cfg with a lot of comments: server.cfg on csgodev For further fine tuning at the game modes you should read the official tutorial wikipedia page from Valve about this: CS:GO Server gamemodes I also want to provide my own server.cfg file here. It’s rather simple and just sets some basic features, like friendly fire and warm up time. You can see my server.cfg file here: server.cfg The server.cfg has to be stored in the directory cfg which is a subdirectory of the csgo_server directory, the directory which we had chosen while downloading the CS:GO server software.
Enough of the words. I wish you a good time in CS:GO and best wishes for you and your server 🙂
Image source: openvpn.net Did you ever wanted to automatically do something after you OpenVPN client has successful connected to your OpenVPN server? To do so you can just add 2 simple lines to your client OpenVPN file:
This 2 lines above are doing the following:
script-security 2: Allows the calling of built-in executables (ip, route, ifconfig, …) and user-defined scripts (see next line). A script-security of 1 would mean that only built-in executables are allowed to be called.
up postscript.sh: This line defines the script which should be started after the client successfully connected to the server. In this case the script is called postscript.sh. If you don’t define the total path to the script here, the script has to be in the same directory as the OpenVPN client configuration.
And that’s it. After you are connected to your OpenVPN Server the given script will be fired up. Don’t forget to make the script executable for course. For e.g. I use this to create a route on specific clients after they connected to the OpenVPN server. Of course you can do whatever you want inside the script.