Howto: TeamSpeak 3 server in pfSense 2.x(Now with scripts amd64) v1.3
-
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?
-
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.
-
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.
-
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?
-
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). -
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.
-
That is a known issue. It was a page or two back when someone caught the change.
-
OPJohnny - have you abandoned the idea of making a package for this vs manually handling it with scripts?
-
Outside of my skillset, honestly. I'm a Microsoft sysadmin that just dabbles in this stuff.
-
Fair enough, I understand completely.
-
Just wanted to say that after I manually extracted and renamed the 64 bit file the script worked great!
-
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.
-
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
-
@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!
: -
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?
-
You'll be needing this on your WAN interface (see arrow) :
Instead of the '1194' port you'll be using '9987' - protocol is UDP.
-
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?
-
I went ahead and posted v.1.3 and updated the first post. Enjoy! :)
-
I think updating the current one is the right choice.. :)
-
Teamspeak's exploding license servers are a bummer but the upgrade to 3.11.0 was nice and smooth!
