Topic: TeamSpeak server on SME (moved)

[william_syd]

Can you connect on the lan side ?

[boss_hog]

Hi William,

Can you connect on the lan side ?

Yes I can.

Since my previous post I have gotten TS to work.
And I *may* have found a bug in the Port Forwarding Panel.
As it turned out the Port Forward rule was not being applied from the Server Manager.
When I went into the console and ran the commands:

expand-template /etc/rc.d/init.d/masq
service masq restart

It started working as expected. I will be visiting the Bug Tracker later on tonight.
Thanks
Joe

[Lourens]

@boss_hog,

Did you put this in the bugtracker? (I cannot find it)

followed the how-to on a clean 7.1.2 server (server-only) and cannot reach the server from the wan side.  
When i do a service masq stop, then it is reachable so the problem has to do something with port-opening.

Is this the same problem you had. Can you please name the bug ID (or tell me what I am doing wrong)

Lourens

[boss_hog]

Hi Lourens,

Did you put this in the bugtracker? (I cannot find it)

No, sorry, I did not.
After making that post and looking through my logs, it was obvious that my SME7 production machine(PM) was forwarding the port.

What I could not figure out, was why the SME7 testbox(TB) was ignoring the forward. The Teamspeak server did start working, however.

After upgrading my SME7(TB) to 7.1.2, the Teamspeak server is not respongding, again.
I may have a little time next week to look at this gem again.
Joe

P.S. for the record, at the moment my TS server is accessible from the LAN, but is not reachable from the WAN.

[Lourens]

Boss_hog,

I have  the same problems on 2 (server-only) servers that I upgraded from 7.1 to 7.12. Not accesible from WAN. I have not enough knowledge to define what may have caused this, so I hope you can make a bug report.

Lourens

[cool34000]

Hi there !

It looks like TS is working in server+gateway mode but it's not working anymore on a server-only SME. On a serveronly SME, I can also connect from LAN but not from the outside...
Could this be caused by the template 42AllowTS ?
I'm wondering if this template is really needed... Should the port (8767 UDP) be opened with the conventionnal command

config set teamspeak service status enabled UDPPort 8767 access public

Can someone confirm the command is good/will work ?

[william_syd]

I would get rid of the template, set the db with your command and do a signal-event remoteaccess-update

I'm not using TS at the moment.

[nicocha]

Hi there !

It looks like TS is working in server+gateway mode but it's not working anymore on a server-only SME. On a serveronly SME, I can also connect from LAN but not from the outside...
Could this be caused by the template 42AllowTS ?
I'm wondering if this template is really needed... Should the port (8767 UDP) be opened with the conventionnal command

config set teamspeak service status enabled UDPPort 8767 access public

Can someone confirm the command is good/will work ?

In my case, i used teamspeak in server only mode too. And it work with SME 7.1.1. btu when i upgrade to sme 7.1.2, it doesn't work. I can access to teamspeak with LAN but not with WAN. I have a tools in other internet site that indicate to me that teamspeak is runing with test on 8767 port. But nobody can connecte to my server even if i think tha 8767 port is open.

http://www.tsviewer.com/index.php?page=ts_viewer&ID=19155

Is there a link where i can test that 8767 port is open in both direction?
is there on SME 7.1.2 something to indicate that this port is for a service (teamspeak)?  Is there with iptables a restriction to all UDP port?

Thank for respond.
Sorry for my poor english (i am french)

[nicocha]

As i use the SME serveur behind a routeur that make firewall. I desactivat the masq service and teamspeak can be access by WAN area.

It is strange to have a firewall on a server that is in green area.

Nicocha

[william_syd]

Q:   Which ports does the server use?   

A:   

Voice   TeamSpeak 2 client:   8767 UDP   
Webinterface   Browser: http://server_ip:webinterface_port   14534 TCP   
HTTPServer Port=12345
TCP query   telnet server_ip tcpquery_port   51234 TCP   

To get your server working behind a router/firewall you only need to forward/open port 8767 UDP (not TCP).

Q:   Some people can't connect to my server, some can. How to fix?   

A:   
Symptoms:

    * People who are using a home router (NAT) CAN'T connect to your server, but they CAN connect to other servers.
    * People connected directly to the internet, CAN connect to your server.
    * The machine that is running the server has more than one external ip number.


The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary ip). Nat routers don't know what to do with this foreign incoming data (unknown ip+port), and drop the packets.

Solution:

    * Open the file server.ini that is created in the same directory where the server executable is located.
    * Look for the following line in section [Main Config]:

      BoundToIp1=

    * Modify it like this:

      BoundToIp1=213.202.254.117

This will make the server listen and send only on the specified address. Even easier is to let the clients connect to the primary IP of the machine.

Note: You can bind the server to multiple IP addresses by adding additional BoundToIp options (i.e. BoundToIp2, BoundToIp3, etc.) to your server.ini.

[Lourens]

Q: Which ports does the server use?

A:

Voice TeamSpeak 2 client: 8767 UDP
Webinterface Browser: http://server_ip:webinterface_port 14534 TCP
HTTPServer Port=12345
TCP query telnet server_ip tcpquery_port 51234 TCP

To get your server working behind a router/firewall you only need to forward/open port 8767 UDP (not TCP).

Q: Some people can't connect to my server, some can. How to fix?

A:
Symptoms:

* People who are using a home router (NAT) CAN'T connect to your server, but they CAN connect to other servers.
* People connected directly to the internet, CAN connect to your server.
* The machine that is running the server has more than one external ip number.


The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary ip). Nat routers don't know what to do with this foreign incoming data (unknown ip+port), and drop the packets.

Solution:

* Open the file server.ini that is created in the same directory where the server executable is located.
* Look for the following line in section [Main Config]:

BoundToIp1=

* Modify it like this:

BoundToIp1=213.202.254.117

This will make the server listen and send only on the specified address. Even easier is to let the clients connect to the primary IP of the machine.

Note: You can bind the server to multiple IP addresses by adding additional BoundToIp options (i.e. BoundToIp2, BoundToIp3, etc.) to your server.ini.

@boss_hog and Nicocha; Was this the solution for your problem. I can still not connect on the WAN site. Do you have the same problems or am I doing something wrong? I didn't make any changes in teamspeak or my router, problem occured when I did the upgrade from 7.1 tot 7.12

Lourens

[nicocha]

@boss_hog and Nicocha; Was this the solution for your problem. I can still not connect on the WAN site. Do you have the same problems or am I doing something wrong? I didn't make any changes in teamspeak or my router, problem occured when I did the upgrade from 7.1 tot 7.12

Lourens

Has i say, i have stop the masq service. Has you are in serveur mode, behind a routeur (that make firwall) i think you can stop masq (the sme firwall with iptable). (i didn't try william_syd solution because it's work befor upgrade from 7.1 to 7.1.2)

For that i use a contrib "service" but also you can test with the commande
service masq stop

and if it's work delete the SXXmasq link int /etc/rc.d/rc7.d with XX a number.

Nicocha

[cool34000]

Hey !

I'd rather wait for an explanation (there must be one !). It was working before v7.1.2, something must have changed in SME configuration !
I don't think it's a good idea to desactivate the firewall (even if you're in server-only mode).

[bpivk]

I don't think it's a good idea to desactivate the firewall (even if you're in server-only mode).

Server only mode doesn't have a firewall.

[william_syd]

@boss_hog and Nicocha; Was this the solution for your problem. I can still not connect on the WAN site. Do you have the same problems or am I doing something wrong? I didn't make any changes in teamspeak or my router, problem occured when I did the upgrade from 7.1 tot 7.12

Lourens

Has i say, i have stop the masq service. Has you are in serveur mode, behind a routeur (that make firwall) i think you can stop masq (the sme firwall with iptable). (i didn't try william_syd solution because it's work befor upgrade from 7.1 to 7.1.2)

For that i use a contrib "service" but also you can test with the commande
service masq stop

and if it's work delete the SXXmasq link int /etc/rc.d/rc7.d with XX a number.

Nicocha

Thats not really the best way.

Code: [Select]

config setprop masq status disabled
/etc/rc.d/rc7.d/S36masq stop