Monthly Archives: July 2013

You are browsing the site archives by month.

Installing & Configuring A Vanilla Wolfenstein Enemy Territory Dedicated Server On Ubuntu Linux

Background

Wolfenstein Enemy Territory is a free-to-play multiplayer game, based on World War II “Allies vs. Axis” style combat.  It is a first-person shooter game, but it has objective-based gameplay.  Players will perform tasks such as escorting tanks, stealing gold, repairing radio transmitters and delivering stolen documents to the transmitter, building tank barriers, dynamiting protection walls, and other objectives based on the map.  The objective-based gameplay makes Enemy Territory a uniquely fun gaming experience, with the classic FPS aspects gamers crave.  Enemy Territory is not one of those games where you look at your kill statistics, you’re too busy defending your objective or advancing on your enemy!

The Goal of This How-To

At the end of this how-to, you should have a vanilla Enemy Territory running.  You will be able to install Enemy Territory on a Windows client, connect to the server, and play Enemy Territory online!

Installing The Vanilla Enemy Territory Server

First, we need to download the Linux Enemy Territory game files.  It is necessary to install the entire game in order to have a dedicated server, but no GUI is needed, you can do all of this through an SSH session if you choose.

You can obtain Wolfenstein Enemy Territory on various websites on the Internet, but for the purposes of longevity of the links in this how-to, I will use the files hosted on The United Federation of Gaming (as I have control over these files).

Download the game:

wget http://www.unitedfederationofgaming.com/dist/wolfet/linux/et-linux-2.60.x86.zip

Download the latest patch for the game:

wget http://www.unitedfederationofgaming.com/dist/wolfet/linux/ET-2.60b-linux.zip

Extract the Zip files:

unzip et-linux-2.60.x86.zip

unzip ET-2.60b-linux.zip

Make the installer executable:

chmod +x et-linux-2.60.x86.run

Run the installer:

./et-linux-2.60.x86.run

Screenshot - 07202013 - 01:53:06 PM

 

Screenshot - 07202013 - 01:53:22 PM

 

It is okay to continue as a limited user, and install the game in your home folder.

Screenshot - 07202013 - 01:53:34 PM

 

Press the Space Bar to quickly scroll through the license agreement.

Screenshot - 07202013 - 01:54:33 PM

 

Type “Y” and hit Enter to accept the license agreement.

Screenshot - 07202013 - 02:02:26 PM

Press “n” and hit Enter to avoid reading the CHANGES file.

Type in a path to install the game to.  I recommend installing into your home folder, unless you have a good reason not to.  I installed to my home folder, in a folder called WolfET.

When prompted about where to put the symbolic links.  Symbolic links are basically just shortcuts, so this question is very non-important.  I put them in my home folder, in a folder called WolfETLinks.

If you get an error message like “No write permission to /path/to/symlink/folder” make sure the directory exists by using the mkdir command to create it.

When asked about installing the PunkBuster client/server files, type “Y” and hit enter.

Screenshot - 07202013 - 02:09:14 PM

 

Again, use the Space Bar to scroll through the license agreement.  Press “Y” and hit Enter to accept it.

Screenshot - 07202013 - 02:10:29 PM

 

We do not want to install the startup menu entries, so press “n” and hit enter.

Screenshot - 07202013 - 02:11:30 PM

 

Press “Y” and hit Enter to continue the installation.

Screenshot - 07202013 - 02:12:27 PM

 

When the installation is completed, do not start the game now.  Press “n” and hit Enter.

Patch\Update The Game:

The patch files are located in the folder called Enemy Territory 2.60b

cd "Enemy Territory 2.60b/linux"

Copy the two files to the path where you installed Enemy Territory.  This will overwrite the old game files with the patched ones.

cp * /path/to/enemyterritory/

Configuration

The Enemy Territory server is configured by two files primarily: server.cfg and a map rotation cfg of your choice.  You can find these files in the etmain folder.

The vanilla configuration will mostly work for your vanilla server, but there are a few notable settings you might want to change.

server.cfg

Server Access Settings
set sv_maxclients allows you to set the number of slots available to your server.  The default is 20 players.
set g_password sets a join password on the server.  Most servers will want to leave this blank, and doing so is not a security risk.

Server Administrative Settings
set rconpassword sets a remote console password for the server.  You can use this to control the server from the ~ menu in-game.
set refereePassword sets a password to gain “referee” access in game, to change maps and handle basic functions from the GUI.

Server Bandwidth Settings
set sv_maxRate and set sv_dl_maxRate are speed limits.  I usually set them to 9999999999, to provide the best allowable performance to users.

Server Advertisement & MOTD Settings
set sv_hostname sets the name of your server on the Internet lobby.
set server_motd[0-5] sets the Message of The Day (MOTD) for the server.  This is shown during initial connection.  Usually people write server rules or other info here.

For ease of configuration, the rest of server.cfg can be left vanilla until you see a need to tweak it.  An entire post could be written about this file, but these are the basics of what most people will need to change.

Map Rotation Configuration
What I have done in the past, is copy campaigncycle.cfg to a file called servercycle.cfg and do my configuration in there.  For now, we can use campaigncycle.cfg as is the default.  It is possible to make your own custom campaign rotations, but that’s a post for another day.

Launcher
In the past, I’ve discovered that some of the configurations of Enemy Territory out of the box (and set by my own server.cfg) don’t seem to really apply correctly.  So, I’ve used a launcher script to start the game.  Create a file called startet.sh in the root folder (outside etmain, same folder etded.x86 is in) and put your launch instructions in it.  This is my startet.sh:

./etded +set com_hunkmegs 512 +exec servercycle.cfg +set net_ip "192.168.10.5" +exec server.cfg

com_hunkmegs is a reference to the amount of memory you will let the server consume.  I have found that increasing this limit is desirable when running a heavily loaded or modded server.  The rest of that should be fairly self explanatory.  Replace 192.168.10.5 with your server’s IP address.  Replace servercycle.cfg with the map rotation configuration file you made above.  If you renamed server.cfg, change that here as well.

Make the launcher executable:

chmod +x startet.sh

Run the launcher to start your game server.

./startet.sh

You should see a lot of text run down your screen, it will look like this generally:

There will be some errors in this, notably the failure loading qagame.mp.i386.so.  These errors are OK in my experience…

Once you’re up and running, you’ll see some text like this in your console:

^1Warning: setstate called and no entities found is another OK error.  It just means there is no one in the server right now.

Firewall Rules

If your dedicated server is behind a firewall (and I certainly hope it is) you will need to forward a port to allow Enemy Territory traffic.  That port is 27960 by default.

You’re Done!
Congratulations, if you’ve followed this guide, you now have a functional Enemy Territory server!  To play, connect to your server’s IP address or find the game on the Internet lobby.

If you have any questions about anything in this guide, or Enemy Territory server administration in general, please feel free to ask in the comments.  I am not, by any means, an expert on Enemy Territory servers, but I’ve run one for a number of years and I know more about them than the average person, so go ahead and ask questions!  Thanks for reading.

 

 

 

SSH Tunneling on Windows Using PuTTY

Imagine if you will; you are at work or school and you need to access a site, but its blocked. So being the tech savvy person you are you try a proxy tunnel and that too is blocked.  What do you do?

You create an SSH tunnel proxy on your own machine!

First off, in order to do any of this regardless of your Operating System you need:

  1. an SSH Server
  2. a knowledge of how to configure your computer / browser to use the proxy
  3. some knowledge of writing scripts (optional if you want to run stuff when you startup your computer)

 

Now, if you are on linux or mac it is simple as opening the terminal and running:

Then just point your browser or computer system network settings over to 127.0.0.1 port 55555 it will look like this (on firefox):

2013-05-16 15_25_03-Connection Settings

However, if you are an unfortunate Windows OS user, your situation isn’t as easy. Sure, you could install Cygwin to get ssh on windows; but that just takes a lot of time and configuring and who has the patience for that?! So instead you use the easiest SSH tool for windows: PuTTY.

PuTTY is a simple executable file that lets you connect to ssh servers easily and effectively. It also allows you to store “Sessions” with special settings for the servers you connect to, but all that can be looked at on your own; now back to the topic at hand.

In order to make connecting to your server as simple as possible I created a script that can be ran. You can even edit this script to include some other programs you want to “auto-launch” once you have the proxy up and running.

(take care to replace all the necessary variables in the objShell.Run command i.e. Paths, Passwords, Users, etc.)

now copy this code and paste it into a file and name the file WhateverNameYouWant.vbs (the .vbs portion is crucial as it is how the script will be able to execute). Execute the script and then you’re almost done. All that is left is to configure whatever program (as long as it supports a SOCKS5 proxy) to use the proxy.  Again to do it on firefox:

2013-05-16 15_25_03-Connection Settings

Make sure to leave PuTTY up and running, if you close it out it causes your proxy to shutdown as well.

NOTE: configuring your browser to use the proxy in the way shown above will cause all your traffic all the time to be sent through the proxy.  If you want a way to toggle between proxy and no proxy install an addon onto the browser (I recommend FoxyProxy, it’s compatible with both Firefox and Chrome).

 

I hope you have enjoyed this little tutorial and if you have any questions leave a comment down below.

Sample debug output code for BASH/SHELL

When trying to debug your own scripts it can be difficult to see exactly what you want.  Pages of white text scrolling across the screen.  Here is a quick flexible function that can make life a whole lot easier by setting different debug values and instead of using echo, use the function name.

Copy this into a basic script and run it, adjust the debuglevel variable at the top to see different output.  I know this will help me in the future and hope it will help others as well.