Remember that srcds was written for Windows, and on Windows, 26000
actually is in the ephemeral port range, because Microsoft.
Why Valve thought it was appropriate to run their servers in the
ephemeral range? Because potato.
On 7/24/14, 3:27, Jesse Molina wrote:
Unless I am mistaken, that's an "ephemeral" port, in that it's used
for outbound traffic only. So, I don't think you need to explicitly
allow inbound traffic to it, as long as you have a stateful firewall.
I believe that is true of both CLIENTPORT (+clientport) and STEAMPORT
(-steamport). Someone please correct me if I'm wrong here.
No, it isn't documented anywhere.
The only ports you need to allow inbound are HOSTPORT (+hostport) on
UDP, and then TCP if you want RCON, and TVPORT (+tv_port) if you want
Source TV to work (probably not). REPLAYPORT isn't even used on TF2
anymore and I'll remove it from wrench in the future.
Whatever your assign to STEAMPORT, the server will use N+1, because bugs.
On 7/24/14, 2:25, Thibaud Van Hissenhoven wrote:
Hi guys,
I just got into srcds and set up my first cloud server using Mr Molina's
great wrench tool. Now that my vanilla L4D2 server is running, I was
busy
configuring the firewall to allow clients to connect. I noticed the
server
is accepting connections on port 26006 (opposed to -steamport 26005
set in
the arguments), on the developer wiki I couldn't find what this port is
used for. Do any of you have experience with this?
The srcds is listening for connections here right, so I should open the
port in the firewall?
Thanks.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux