Howto: TeamSpeak 3 server in pfSense 2.x(Now with scripts amd64) v1.3

NoOneParticular

Carefull guys Teamspeak has changed their naming schemes, so you have to be careful and make those changes:

for example this latest update 3.0.12.4 as of today:

teamspeak3-server_freebsd_amd64.3.0.12.4.tar.bz2

**problems were: freebsd_amd64 instead of freebsd-amd64 (including the internal folder)
**changed it from a tar.gz to a tar.bz2

So either edit the install script to reflect those changes or, as I did, I changed the name of the file from _ to -, and changed the name of the internal folder from _ to - also, then changed it from tar.bz2 to tar.gz

I just wanted to add, the scripts haven't been updated for this change yet.

I found it easiest to modify the install file and rename the folder within the script after the teamspeak3 server file is decompressed. The script will continue and you'll have less changes to make to the install script.

```
tar -xf /root/teamspeak3-server_freebsd_amd64*.tar.gz
mv teamspeak3-server_freebsd_amd64 teamspeak3-server_freebsd-amd64

2dfx

Anyone else having file i/o issues with TS3 after installing? Can't modify icons or upload files to the server.

All folders within the ts3 server folder in /usr/local/lib have been chown'd recursively to the teamspeak user yet the issue still exists.

opjohnny

Just updated Teamspeak to 3.0.13.6, no issues at all. Still doing it the copy/paste way where I connect via filezilla and drag the contents of the new \teamspeak3-server_freebsd-amd64\ folder in to the usr\local\lib\teamspeak3-server_freebsd-amd64\ folder overwriting everything, with putty open in the background for the backup and ownership commands. This way also doesn't require you to rename anything.

tong

Looks like the newer version don't give root enough permissions for /usr/local/lib

I've tried everything i could on a new install to get it to work with no success. True i have very limited skill and knowledge on freebsd.

Any chance someone could explain how to get it to work on a new install (version 2.3.3 )?

Or maybe we can get an updated script?

opjohnny

I'm up to date on pfsense and no issues with TS, especially after multiple reboots the last few days while trying to open NAT for my xbox. Haven't attempted any TS updates in a few weeks.

tong

I ended up finding an image of 2.2 i had that allowed me to install TS then updated to 2.3.3, trying to figure out why in the new package root does not have permissions with /usr/local/lib to be able to copy the files over and do the rest.

opjohnny

So TS server will only work if it's already installed prior to 2.3.3, and after 2.3.3 you can't install or upgrade the TS server due to the permissions issue?

tong

@opjohnny:

So TS server will only work if it's already installed prior to 2.3.3, and after 2.3.3 you can't install or upgrade the TS server due to the permissions issue?

That seems to be my experience, unless I choose something I shouldn't have during an install. I will test this out later on another box I have just in case.
Seems that root user no longer has enough permissions to /usr/local/lib to copy the folders over (never mind the rest of the stuff it has to do).

tong

It works. You need to edit the "pfsense-teamspeak-install_amd64.sh" and "teamspeak3-server.sh" script and change all instances of

/usr/local/lib/teamspeak3-server_freebsd-amd64

to

/usr/local/lib/teamspeak3-server_freebsd_amd64

That single "-" is what's causing the install issue. It extracts the archive to a folder named "teamspeak3-server_freebsd_amd64" but tries to move a folder named "teamspeak3-server_freebsd-amd64" to that location and obviously that doesn't exist.

Funny thing is it's not the scripts fault cause it's not telling it what to extract it to. Teamspeak changed the folder structure that it extracts. So looks like someone decided not to follow precedent and errors like this happen.

opjohnny

That is a known issue. It was a page or two back when someone caught the change.

iced98lx

OPJohnny - have you abandoned the idea of making a package for this vs manually handling it with scripts?

opjohnny

Outside of my skillset, honestly. I'm a Microsoft sysadmin that just dabbles in this stuff.

iced98lx

Fair enough, I understand completely.

iced98lx

Just wanted to say that after I manually extracted and renamed the 64 bit file the script worked great!

opjohnny

Another problem-free upgrade to 3.0.13.8.

Still using the method where I connect via filezilla and copy the contents of \teamspeak3-server_freebsd_amd64\ to \user\local\lib\teamspeak3-server_freebsd_amd64. Doesn't require any file renames. Never had luck with uploading the tar.gz file and performing an extract via shell.

The command to start the TS server still doesn't work for me either. I just copy the forcestop command, change it to forcestart, and that does the trick.

iced98lx

0_1529257738143_teamspeak_scripts_x64_v1.3.zip

Here is a .zip of 64bit scripts that have been updated for the new naming format. I used them to install 3.2.0 fresh on a 2.4.3_1 install of pfSense but I extracted the TAR and re-compressed it as a gz first, since I didn't want to mess with changing the un-compress command.

NOTE: THIS WILL CREATE A FILE THAT SAYS YOU ACCEPT TS'S LICENSE!

Please read and understand the license terms before using this script, it auto-generates a "License accepted" file.

Thanks!

Chris

Dissonance

@kevev Thank you for these scripts and everybody for this info! I'm brand new to PFsense &FreeBSD but after renaming the new tar file and a making a few edits to the scripts I'm mostly up and running! I can't seem to get TS to start automatically yet but I can start it manually for now. Once I can figure out how to get Crontab to start TS on reboot I think I'll be all set!

Cheers! :

Pixel_47

Hello, I have a PC with pFsense installed and I was able to run Team Speak 3 freeBSD, the server restarts after rebooting the router, but I have a basic question how to open the port to connect to Team Speak 3 from the outside. I should open port 9987 but for ip router?

Gertjan

You'll be needing this on your WAN interface (see arrow) :

Instead of the '1194' port you'll be using '9987' - protocol is UDP.

kevev

Wow! It has been a long time since I updated this post. I forgot to enable email notifications.

I have created an updated version with all of the fixes. Thank You everyone for keeping this thread alive.

Question: Do you all want me to update this tread, or just create a new thread?