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

tong

Done. Good luck with snort. Very powerful product.

How about a set of directions for changing hardware or machines, or even a fresh install upgrade? Some way to carry over our install and current settings? I'm guessing it goes like the upgrade instructions for the first part of it.

Thanks.

kevev

I am guessing you only need to bring over the sqlite* DB file. As this is outside of the scope of this thread maybe try the teamspeak website.

@tong:

@kevev:

Done. Good luck with snort. Very powerful product.

How about a set of directions for changing hardware or machines, or even a fresh install upgrade? Some way to carry over our install and current settings? I'm guessing it goes like the upgrade instructions for the first part of it.

Thanks.

opjohnny

Will updating to 2.2 break the TS server at all?

kevev

Try it and let us know. ::)

@opjohnny:

Will updating to 2.2 break the TS server at all?

tong

@opjohnny:

Will updating to 2.2 break the TS server at all?

Nope works fine.

To move your server to a new machine or if you wish to reformat/reinstall a fresh copy of pfsense:

Do the backup part as Kevev as stated in post 2 for an upgrade (steps 1 through 4), then copy the backup to another computer/location. From this backup all you technically need is ts3server.sqlitedb file. Follow the instructions posted for the install from post 1, on reboot (@ step 8.) do the following:

1. Verify the server is running, connect to it should ask you for the key as in original step 8, don't bother we don't need this.

2. Shutdown the teamspeak server:

a.) /usr/local/etc/rc.d/teamspeak3-server.sh forcestop

3. Copy the original ts3server.sqlitedb file from your backup and override the new one to:

/usr/local/lib/teamspeak3-server_freebsd-x86

or

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

4. Optional: Copy your log folder also and override the new one (I like to keep logs)

5. Start the teamspeak server and verify everything works:

a.) /usr/local/etc/rc.d/teamspeak3-server.sh start

6. If you wish to, restart the router and verify the teamspeak server starts as expected.

***thanks to kevev for making this super easy for us, most of these instructions are just a copy of his.

kevev, you can add this to your second post if you want so people don't have to hunt for it.

kevev

Tong: I linked your post to 2nd post.

Also, I found out that Mumble server(Murmur 1.2.3) is available as a binary install for pfsense 2.1.x . I have some install instructions but there are lots of steps. I will try to make an install script like I did here. Also I haven't checked if Murmur 1.2.8(latest rease) is available for the new pfSense 2.2 . Hoping it is and also compatible with pfSense 2.1.x .

Question: Anyone interested in a freedns install script?(freedns.afraid.org) I have seen lots of people asking for a solution for this free dynamic dns service. I use it so people can connect to my TS server via URL instead of always changing IP.

tong

@kevev:

Tong: I linked your post to 2nd post.

Also, I found out that Mumble server(Murmur 1.2.3) is available as a binary install for pfsense 2.1.x . I have some install instructions but there are lots of steps. I will try to make an install script like I did here. Also I haven't checked if Murmur 1.2.8(latest rease) is available for the new pfSense 2.2 . Hoping it is and also compatible with pfSense 2.1.x .

Question: Anyone interested in a freedns install script?(freedns.afraid.org) I have seen lots of people asking for a solution for this free dynamic dns service. I use it so people can connect to my TS server via URL instead of always changing IP.

I though that that could be done already in dynamic dns clients? I'm using an old dyndns account I've had for over a decade to do the resolving

kevev

That is true. Just offering another option that pfsense does not support.

iced98lx

Does this run TS in a jail? I know running TS on my firewall will obviously provide one more possible place to compromise the system but if it's in a jail and not running as root I'd be willing to give it a shot.

kevev

@iced98lx:

Does this run TS in a jail? I know running TS on my firewall will obviously provide one more possible place to compromise the system but if it's in a jail and not running as root I'd be willing to give it a shot.

No jail. They are easy to set up though.

iced98lx

@kevev:

@iced98lx:

Does this run TS in a jail? I know running TS on my firewall will obviously provide one more possible place to compromise the system but if it's in a jail and not running as root I'd be willing to give it a shot.

No jail. They are easy to set up though.

Cool, would be neat to see this package-tized & jailed for easy installation and management but great work getting it all going will be installing and the effort is appreciated.

opjohnny

I'm going to attempt an update to pfSense today. Kev, what steps would you recommend I follow in order to retain my settings/unique key through the update?

Also, are there any easy ways to make running this server on my pfSense box any more secure? Simple stuff like firewall rules or at least some basic things that don't leave the rest of my network open to attacks through the TS server. Right now I only have the one LAN that goes through an Asus RT-N56u that serves my main rig, 2x smart Bluray players, 1x Chromecast, 1x Android tablet, 1x Android phone. The proper solution here is to not host TS on the pfSense box, but it's my only option for the foreseeable future. It's going to be a while before I get my new rack installed and all my server hardware back online.

ETA: Also, what would be required if I decide to change hardware for pfSense? Eventually I plan to get one of those small devices from aliexpress to mount to my network panel and I would very much like to keep my TS server and not have to reconfigure everything from scratch. I know I can export/import my pfSense settings, just curious about the TS server. Would I have to do something like download a specific folder, install TS on new pfSense box, upload that specific folder?

kevev

Post #2 has everything you are looking for. You can tar up the install which will backup the sqlite database.

@opjohnny:

I'm going to attempt an update to pfSense today. Kev, what steps would you recommend I follow in order to retain my settings/unique key through the update?

Also, are there any easy ways to make running this server on my pfSense box any more secure? Simple stuff like firewall rules or at least some basic things that don't leave the rest of my network open to attacks through the TS server. Right now I only have the one LAN that goes through an Asus RT-N56u that serves my main rig, 2x smart Bluray players, 1x Chromecast, 1x Android tablet, 1x Android phone. The proper solution here is to not host TS on the pfSense box, but it's my only option for the foreseeable future. It's going to be a while before I get my new rack installed and all my server hardware back online.

ETA: Also, what would be required if I decide to change hardware for pfSense? Eventually I plan to get one of those small devices from aliexpress to mount to my network panel and I would very much like to keep my TS server and not have to reconfigure everything from scratch. I know I can export/import my pfSense settings, just curious about the TS server. Would I have to do something like download a specific folder, install TS on new pfSense box, upload that specific folder?

opjohnny

@kevev:

Post #2 has everything you are looking for. You can tar up the install which will backup the sqlite database.

Thanks Kev! Backed up the TS directory, ran the update, TS came back online with pfSense with no issues. 8)

opjohnny

Backed up my TS directory and updated to pfSense 2.2.1. Absolutely no issues. 8)

opjohnny

Backed up TS, upgrade to pfSense 2.2.2 went without a hitch, then realized TS 3.0.11.3 was available so continued instructions in post 2 for an actual TS upgrade, but ran in to an issue at the step where I extract the tar.gz file in /root/ to /user/local/lib.

tar -xzvf teamspeak3-server_freebsd-x86-*.tar.gz -C /usr/local/lib

tar: teamspeak3-server_freebsd-x86-3.0.11.3.tar.gz: Not found in archive
tar: -C: Not found in archive
tar: /usr/local/lib: Not found in archive
tar: Error exit delayed from previous errors.

Then after I started the TS server back up it was taking a long time, rebooted, same issue. Saw the TS processes running in the webGUI. Did a forcestop, tried start a few times, eventually the server came back up. When I connected to it I was given a popup notice about the server identity changing and asking me if I accept the new identity and want to remain connected. Not exactly sure what happened here.

ETA: I stopped the server, unzipped the tar.gz on my desktop, then unzipped the .tar on my desktop, then copied that folder over to /usr/local/lib/ via FileZilla, issued the chown command, then rebooted pfSense since I always have trouble manually starting the server for some reason. The server came online a few minutes after rebooting the box. Viewing Server Connection Info in my TS client shows version 3.0.11.3.

For anyone having a similar issue with the tar command just download FileZilla(the .zip option, not .exe since the latter includes bloatware) and connect to your router IP using port 22. Make sure SSH is enabled in Advanced Settings of pfSense and under that no port is chosen, otherwise if you set a port use that port to connect with FileZilla. Then just drag and drop the TS folder to /usr/local/lib/ and choose the overwrite option for all files in queue.

opjohnny

Haven't upgraded in a while but due to pfSense 2.3 being released I'd figure I'd give an update on how things are working in case others are still hosting TS on their pfSense box or will do so.

The upgrade to TS Server 3.0.12.3 went without a hitch. I just followed the upgrade instructions except for the extraction part. For that I still unzipped the folder and copied its contents to the folder un \usr\local\lib\ in FileZilla, making sure to overwrite all. You also need to add an ".sh" to the end of "server" in the start command in the instructions otherwise it will fail as an unknown command.

After the upgrade to pfSense 2.3 the TS server came right back up on its own as expected, so this method still works great.

Thanks again, Kevev. 8)

tong

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

NoOneParticular

@tong:

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.