Linux SRCDS port problems

[jasteele]

Hello. I am running a linux server for Counter-Strike Source and I can get the server to run, but it is not running properly. To be specific, my router (I guess) will constantly assign a weird public port to the server that is usually in the 63000 range. This prevents the server from being a true "dedicated" server in the sense that the IP address is changed every time I restart the server. I tried specifying a port in the "-port" switch in the command line when starting the server but my server just refuses to start with an error message telling me that it cannot allocate a dedicated UDP port for the server. Also, I HAVE to reconfigure my router every time I start the server to forward the ports the server is using. For example, if the router assigns the port 63440 to the server, I will go in an forward the public port 63440 to the private port 27015. I also do the same thing for 63435 ---> 27010 and 63445 -----> 27020. I am also forwarding the public to private IP address in each instance. Another problem I have with the server is that I cannot use RCON on the server. typing "status" in the console in game or on the server just gives me what I suppose is the subnet mask and does not give me the public or private IP. My server also has DMZ activated on it.

Does anybody have any suggestions as to how I can get my router to assign a static port to my server and how my server can work with RCON commands? Any help would be greatly appreciated.

By the way, I am running the server on CentOS 4.1 (http://www.centos.org) and my router is a D-Link DI-524. Thanks for any help!

[cryotek]

are you using +ip ?

[twinsen]

All i know is that when i had the UDP port problem i just forwarded the correct ports and it dissapeared.
I duno if cent uses iptables for the firewall but if you have a firewall that could be blockling it.

[jasteele]

Using my public IP gives me errors and srcds tries to restart. Using my private IP sometimes works but that's not the IP that shows up in STEAM... Also, if I specify no ports or IPs it will work but not properly. When I try to specify the port, it sometimes works but it doesn't change the public port anyway.

Thanks for all of your replies so far!

Oh, and cryotek, when I say "Using my public IP" I mean that I am using +ip xx.x.xxx.xx as a command line switch, just with those IP's.

[cryotek]

Quote:sing my private IP sometimes works but that's not the IP that shows up in STEAM..

what do you mean?

[unhallowed]

jasteele Wrote:Hello. I am running a linux server for Counter-Strike Source and I can get the server to run, but it is not running properly. To be specific, my router (I guess) will constantly assign a weird public port to the server that is usually in the 63000 range. This prevents the server from being a true "dedicated" server in the sense that the IP address is changed every time I restart the server. I tried specifying a port in the "-port" switch in the command line when starting the server but my server just refuses to start with an error message telling me that it cannot allocate a dedicated UDP port for the server. Also, I HAVE to reconfigure my router every time I start the server to forward the ports the server is using. For example, if the router assigns the port 63440 to the server, I will go in an forward the public port 63440 to the private port 27015. I also do the same thing for 63435 ---> 27010 and 63445 -----> 27020. I am also forwarding the public to private IP address in each instance. Another problem I have with the server is that I cannot use RCON on the server. typing "status" in the console in game or on the server just gives me what I suppose is the subnet mask and does not give me the public or private IP. My server also has DMZ activated on it.

Does anybody have any suggestions as to how I can get my router to assign a static port to my server and how my server can work with RCON commands? Any help would be greatly appreciated.

By the way, I am running the server on CentOS 4.1 (http://www.centos.org) and my router is a D-Link DI-524. Thanks for any help!

I had the same exact problem and it turned out the culprit was my DLink router. Read here http://forums.srcds.com/showthread.php?tid=747