View Full Version : risks for forwarding these ports?
are there any dangers for forwarding these ports?
teamspeak:
14534 UDP/TCP
8767 UDP/TCP
51234 UDP/TCP
blizzard battle.net :)
6112-6119 UDP/TCP
If only TS uses it, no.
Do not forward the 51234 port if you do not need it, though.
Just to make sure you do not need for forward the ports if you are a client, only the server needs to have those ports forwarded.
134hlm4n
23-06-2007, 14:04
are these the only ports that need forwarding?
ANR Daemon
23-06-2007, 14:13
Only one port You ABSOLUTELY NEED to forward is 8767/udp (or whatever You use... I assume You use default port).
PROBABLY You need to forward 14534/tcp which allows user/SA to access web-interface of Your server.
DO NOT forward 51234/tcp until You ABSOLUTELY SURE You need that forwarding.
134hlm4n
23-06-2007, 14:51
now i will reveal my intelligence with compys, where/how do i forward these ports
ok i closed 51234 UDP port i have to have tcp open in order to use the tsadmin client :/ is that ok?
All you need to do is allow your computer to access the ports. The ports can be open at the computer, just do not forward the ones that you do not want to use.
ok this is my updated port forwarded list
8767 UDP
14534 TCP
51234 TCP
what do u mean that i can open the ports from my computer? the frist 2 ports is a must right? since i need them to turn on my server and the 51234 one is needed for perlmod and admin client but what do u mean that i can open the port from my computer and dont need to forward them
If you are running the perlmod on the same computer that is running the ts server program then you can leave the ports open on your computer with the firewall, but you can stop people from accessing these ports from the internet by not forwarding them.
The 8767 is needed. That is the one for voice.
The 14534 is the one for server management, but if you are updated, if anyone tries to use brute force will be banned if they do not get it correct in so many tries. You only really need this if you have an SA that, is outside of the lan, you want to allow access to the webadmin.
The 51234 is the telnet port that could be a security risk for you. Most of the time no one uses it anyway as you have to use commands and most are not comfortable, but it is great for scripts as they can do so much with the port. All you have to do is not forward the port from the router and all you computers inside the lan can access the port, and no one outside could connect.
ANR Daemon
24-06-2007, 05:12
Ok, some definitions:
"Allow access" on server machine means that it configured to be able to receive connections to specified port from outside of it. (Note: excepting some rare configs, You always can access Your local services by connectiong to localhost:someport from same computer as where Your services running)
"Forward pors" on router means (in general) that someone in external (global) network (typically named WAN) can access Your local services at host:port inside Your local network by accessing Your router on some port.
So, when You need to manage Your TS service from local network, You should "Allow access" to ports but You not need to "forward ports", because there's nothing to deal with external network.
"Et vice versa" (c), to get users connected to Your server from inernet, You should "Allow access" and "forward port" so users from outside of Your network can come in and get access to service.
im dont really understand how i can turn on my perlmod and admin client without forwarding the port 51234 and opening it from my computer so im doing this temporarily till i understand:
forward port 51234
open perl mod + admin client
unforward port 51234
If your server, perlmod, and admin client is inside the lan then you can use the LAN ip and port number without having to use the router to forward the ports.
Using ports inside a LAN does not require ports to be forwarded if you use the LAN IP and not the wan ip.
yea its inside the LAN what ip is this:
connection for my perlmod:
ServerAddress=(the ip from www.whatismyip.com)
ServerTCPPort=51234
ServerUDPPort=8767
connection for admin client:
server address: (ip from www.whatismyip.com):8767
tcp query: 51234
http: 14534
If you are using the perlmod and the admin client on the same computer that is running the server then you can use.
127.0.0.1 as an ip address.
If you are on another computer inside the lan then you can use the LAN address which might look something like. 192.168.1.5
vBulletin® v3.7.3, Copyright ©2000-2009, Jelsoft Enterprises Ltd.