I did verify that my SRCDS instances are exhibiting exactly the port behaviour
you all mentioned.
I will be modifying more scripts (subtract one from port I number I want to
actually use) for Source-based servers accordingly.
I spend most my my time working with the GoldSrc/HLDS equivalents (+po
Note that I am a Linux-only server admin. I know nothing about the
Windows variant. Sorry, I forget to look at which mailing list I am
talking to. My info may not be applicable to yourself.
One thing to note on the Linux side is that the srcds_run script, unless
-norestart is specified, w
Many thanks for the strictportbind hint, I wasn't aware of that one.
On Nov 1, 2012 2:18 AM, "Jesse Molina" wrote:
>
> This bug has existed for at least the last three years, probably more. I
> don't know if it ever worked right.
>
> Whatever port you assign for -steamport will not be used. Inst
This bug has existed for at least the last three years, probably more. I
don't know if it ever worked right.
Whatever port you assign for -steamport will not be used. Instead, it
will be n+1.
Here is a real example taken from a TF2 server on GNU/Linux...
Process command arguments:
./srcds
Yes, if you set steamport to 27115 it will actually use 27116 to talk to
Steam servers. Not sure when this started but it is like this for at least
two years already. There is a server variable which supposedly tells srcds
to use -port for Steam communication, sv share master something, cannot
reca
First off-, thanks for the replies. A couple of follow-up
questions, for anybody who may know ...
Original information [clarified]:
> I have been using these parameters in the
> command-line for some time [years], to explicitly
> specify what ports to use
You have another server eunning that is using those ports.
-ics
- Alkuperäinen viesti -
> I have been using these parameters in the command-line for some time, to
> explicitly specify what ports to use for the game and for Steam
> communication:
>
> +port 29016
> -steamport 29116
>
> Th
These are clientport and tv_port. For some reason srcds uses steamport+1
instead of steamport.
On Oct 31, 2012 8:48 AM, "Weasel" wrote:
> I have been using these parameters in the command-line for some time, to
> explicitly specify what ports to use for the game and for Steam
> communication:
>
>
I have been using these parameters in the command-line for some time, to
explicitly specify what ports to use for the game and for Steam communication:
+port 29016
-steamport 29116
Those ports are explicitly open on by firewall, etc.
While troubleshooting some other issues (that I think are un-
9 matches
Mail list logo
