Topic: How do I allow public access to TeamSpeak on SME 6.0?

[Karl P.]

I am trying to setup TeamSpeak RC2 on my SME 6.0 server. I have it up and running for my local network, but it is not accessable from the Internet. I tried various port forwarding rules to either 127.0.0.1 or the internal IP address, but these don't work.

The ports are: TCP:14534, 51234 & UDP:8767

Any help is greatly appreciated.

[ldkeen]

Hey Karl,
#mcedit /etc/e-smith/templates/etc/rc.d/init.d/masq/42AllowTS
add the folloing:
/sbin/iptables --append INPUT -p udp --dport 8767 -i $OUTERIF -j ACCEPT
followed by:
#/sbin/e-smith/expand-template /etc/rc.d/init.d/masq
#/sbin/e-smith/signal-event reboot

[Karl P.]

Thanks for the info, I'll try it this weekend. For the TCP ports would I just add the following as well?

/sbin/iptables --append INPUT -p tcp --dport 14534 -i $OUTERIF -j ACCEPT
/sbin/iptables --append INPUT -p tcp --dport 51234 -i $OUTERIF -j ACCEPT


I'll try it out and see if it works. I'll post the results.

[ldkeen]

Karl,
The above is all that's required. I had to set this up for a mate abouth 4 months ago on 6.0b3 and it's been going fine. It does chew a bit of data though, he ended up shutting it down as it was eating up his monthly limit although a lot of providers now offer unlimited downloads.

[Karl P.]

Thank you for your help. The above steps worked.
As far as bandwidth, the server is on a T1 line at my office that is used only for e-mail, no byte limits  

[reiniero]

Karl, could you tell us which method you used to install Teamspeak? Did you modify startup scripts/templates to have it started automatically?
Where did you install the server and did you use MySQL or the built in SQL server?

I'm trying to install Teamspeak RC2 2.0.20.1it on my SME 6.01-01 server, and want it to run as safely as possible.

(Have got it working, kind of, by following these steps:
login as root
adduser tss
cd /home/tss
wget ftp://webpost.teamspeak.org/releases/ts2_server_rc2_20201.tar.bz2
tar -jxvf ts2_server_rc2_20201.tar.bz2
chown tss:tss *
su tss
starting with start script or ./server_linux works, although some error messages are shown
)

Regards,
Reinier

I am trying to setup TeamSpeak RC2 on my SME 6.0 server. I have it up and running for my local network, but it is not accessable from the Internet. I tried various port forwarding rules to either 127.0.0.1 or the internal IP address, but these don't work.

The ports are: TCP:14534, 51234 & UDP:8767

Any help is greatly appreciated.

[Anonymous]

Karl, could you tell us which method you used to install Teamspeak? Did you modify startup scripts/templates to have it started automatically?

[/quote]

Reiniero, I put the startup script in the /etc/rc.d/rc.local file.  It starts up teamspeak after all other programs are started.

It might not be pretty but it works for me.

Jeff P

[pen25]

is there not a contrib for this? I am wanting to setup a backup teamspeak server incase the main goes down and figured since my server is pretty stable and low activity i thought id do this for a friend. is there a how-to for dummies on this?

[StPurple]

Hmmm...

I want to set up a server to...Same problem here. I can connect from my internal network but not from the outside. I've added that line to the firewall rules to open up the udp port. How can I check that it's indeed open and accepting connections?

[pen25]

wouldnt running a scan from grc?

[StPurple]

That's what I've tried but GRC only scans tcp ports...not udp  :{

I've also tried a tcpdump, not sure if it would poop up in that one.....

[arne]

http://scan.sygate.com/preudpscan.html

Please inform how teamspeak works on the sme !

It's equivalent to the Ventriloserver ?

Any certain reason to prefer one in front of the other ?

(Have so fare tried none of them, but would like to try soon.)

Arne.

[StPurple]

the sygate scan shows nothing.....
How can I check on the server itself that the rules is loaded. Should't there be a log file of some stuff?

b.t.w it runs fine on the local network....but I don't need there..al the comps are in the same room.   :}

[arne]

Log on as root via console or via ssh shell.

Commands:

iptables -L

and

iptables -t nat -L

Should give you a view of the existing fw rules.

[CharlieBrady]

Thanks for the info, I'll try it this weekend. For the TCP ports would I just add the following as well?

The TeamSpeak FAQ says that you only need to open the one UDP port. A custom template, as has been suggested, is the way to do it.

[girkers]

arne,

I have loaded Ventrilo onto my server (Server only mode) 6.01-01 custom and it worked fine.  The only issue was setting up the client on the windows end.  I was trying to use the smallest amount of bandwith as possible but were having some issues with the client end.

Server worked fine, but some minor config issues with the client.

The difference from my reading is that Teamspeak will allow as many users as you like for free, where as Ventrilo will only allow 8.  Also the TSS tells the client what codec to use, whereas Ventrilo you need to configure it.  Also the bandwidth used by TSS is higher than Ventrilo.

If you want me info on how I install Ventrilo please email me and I will see if I can find my how to I wrote at home.

[StPurple]

When i use iptables -L this is what I see.....

Code: [Select]

Chain INPUT (policy DROP)
target     prot opt source               destination
state_chk  all  --  anywhere             anywhere
local_chk  all  --  anywhere             anywhere
PPPconn    all  --  anywhere             anywhere
DROP       all  --  BASE-ADDRESS.MCAST.NET/4  anywhere
DROP       all  --  anywhere             BASE-ADDRESS.MCAST.NET/4
ACCEPT     udp  --  anywhere             anywhere           udp dpt:8767
InboundICMP  icmp --  anywhere             anywhere
denylog    icmp --  anywhere             anywhere
InboundTCP  tcp  --  anywhere             anywhere           tcp flags:SYN,RST,ACK/SYN
denylog    tcp  --  anywhere             anywhere           tcp flags:SYN,RST,ACK/SYN
InboundUDP  udp  --  anywhere             anywhere
denylog    udp  --  anywhere             anywhere
ACCEPT     udp  --  anywhere             anywhere           udp spts:bootps:bootpc
gre-in     gre  --  anywhere             anywhere
denylog    gre  --  anywhere             anywhere
denylog    all  --  anywhere             anywhere
And a lot more offcourse...
Does this mean that the port is indeed open and accepting connections?
Cause if that's the case...Why can't I connect to it???

[Unlotto]

Hey Karl,
#mcedit /etc/e-smith/templates/etc/rc.d/init.d/masq/42AllowTS
add the folloing:
/sbin/iptables --append INPUT -p udp --dport 8767 -i $OUTERIF -j ACCEPT
followed by:
#/sbin/e-smith/expand-template /etc/rc.d/init.d/masq
#/sbin/e-smith/signal-event reboot

I have Shell Access to a SME Server 6.0.1-01 and have trouble getting access to my running teamspeak-server

What is the difference between using

the Firewall Management system (through the text gui)
and
doing the above?

Neither will work for me even though I set up a shoutcast-server by simply opening the ports through the ui - somehow this won't work with teamspeak.

Edit: Hmm ventrilo just worked, no funny business

[StPurple]

Bump.......


Dropped the subject for a while...but now the teamspeak server that we normally use died.....

Still having the same problems....

[briant]

I made an attempt at this as well. I was unable get the port opened. Here is the tale of my short lived journey.
http://forums.contribs.org/index.php?topic=28830.msg120016#msg120016
I would love to have this working, but I have exhausted my limited skills.

[l_doddrell]

Hi guys,

Sorry this is a little old, but I really want to keep SME Server.  I too have this this issue and have identified it as being some default rule on the server itself.

My server is 192.168.1.254.  Using GRC I tested each port to find that anything destined to other machines at 192.168.1.1 or ...1.2 for example, worked.  But anything heading for the server itself (...1.254) was blocked.  Therefore a rule must be in place that stops anything from heading to the server.

Surely if the web interface has a forwarding rule in place this default rule should be overidden?

How do we go about doing this?

*UPDATE* SME Server 7.0 (RC2) appears to correct this.  The web admin forwarding rules now read as "localhost" rather than the IP addy of the server.  Well done guys!

Regards.

[yon]

....

[yon]

i have installed the server as discribed in this guide here http://forum.goteamspeak.com/showthread.php?t=15438 and i can start the service can connect to the server and it all works great but peopple outside my network cat access it.    the ports are all forwarded right and everything. i think there is something stopping me from accessing it from outside the network. it is only a server on the network it is behind a smoothwall that has the port 8767 the defult port open to it. but people can seem to connect still.[/url]