Re: [hlds] SRCDS not honoring -steamport parameter any more?

[Jesse Molina]

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, will auto-restart the server over and over 
again if -strictportbind is specified and if a conflict is detected. 
That is probably not desirable.


Thus, it may be wise to build your own script to replace srcds_run or 
just call srcds_linux directly, with the right environment.




Roman Hatsiev wrote:

Many thanks for the strictportbind hint, I wasn't aware of that one.

On Nov 1, 2012 2:18 AM, "Jesse Molina" mailto:je...@opendreams.net>> 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.  Instead,
it will be n+1.

Here is a real example taken from a TF2 server on GNU/Linux...

Process command arguments:
./srcds_linux -game tf -ip x.x.x.x +clientport 27017 +hostport 27117
+tv_port 27217 -steamport 26017 +replay_port 27417 -strictportbind
-pidfile /path/to/my/server.pid -maxplayers 25 +map cp_dustbowl

Now, here is what lsof said is actually in use:

lsof -i 4 -n -a -p $GAMESERVPID
COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
srcds_lin 18039 hlds7u  IPv4 1132076712  0t0  UDP x.x.x.x:27117
srcds_lin 18039 hlds8u  IPv4 1132076713  0t0  UDP x.x.x.x:27017
srcds_lin 18039 hlds9u  IPv4 1132076714  0t0  UDP x.x.x.x:27217
srcds_lin 18039 hlds   10u  IPv4 1132076715  0t0  TCP
x.x.x.x:27117 (LISTEN)
srcds_lin 18039 hlds   11u  IPv4 1367389900  0t0  TCP x.x.x.x:26018



My command specified "-steamport 26017", but 26018 is actually in use.



My solution for this is to simply space out all servers by odd
numbers when running multiple servers on the same IP.  So, I've got
a server at 2xx13, 2xx15, 2xx17, 2xx19, etc

Also note the use of "-strictportbind" above.  This feature was
added at my request by Valve, who graciously answered my call to do
so.  By default, the srcds application happily tramples on ports and
just assigns itself whatever the heck it pleases to have.  When
-strictportbind is used, in theory, the app is supposed to exit with
an error, as any sane and reasonable daemon would.

For verification, I nmap my own host and diff the output against the
previous output and get mailed if differences are found.  That way I
know if anything is gone amiss.



Roman Hatsiev wrote:

These are clientport and tv_port. For some reason srcds uses
steamport+1
instead of steamport.

On Oct 31, 2012 8:48 AM, "Weasel" mailto:wea...@weaselslair.com>
__>> 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:

 +port 29016
 -steamport 29116

 Those ports are explicitly open on by firewall, etc.

 While troubleshooting some other issues (that I think are
 un-related), I noticed these errors in the logs:

 WARNING: Port 27005 was unavailable - bound to port 27006
instead
 WARNING: Port 27020 was unavailable - bound to port 27021
instead

 What are those ports all about?
 Is it not using the -steamport parameter?
 or is this yet more communication of some other form?

 _
 To unsubscribe, edit your list preferences, or view the list
 archives, please visit:
https://list.valvesoftware.__com/cgi-bin/mailman/listinfo/__hlds




_
To unsubscribe, edit your list preferences, or view the list
archives, please visit:
https://list.valvesoftware.__com/cgi-bin/mailman/listinfo/__hlds



--
# Jesse Molina
# Mail = je...@opendreams.net 
# Cell = 1-602-323-7608



_
To unsubscribe, edit your list preferences, or view the list
archives, please visit:
https://list.valvesoftware.__com/cgi-bin/mailman/listinfo/__hlds




___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-

Re: [hlds] SRCDS not honoring -steamport parameter any more?

[Roman Hatsiev]

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.  Instead, it
> will be n+1.
>
> Here is a real example taken from a TF2 server on GNU/Linux...
>
> Process command arguments:
> ./srcds_linux -game tf -ip x.x.x.x +clientport 27017 +hostport 27117
> +tv_port 27217 -steamport 26017 +replay_port 27417 -strictportbind -pidfile
> /path/to/my/server.pid -maxplayers 25 +map cp_dustbowl
>
> Now, here is what lsof said is actually in use:
>
> lsof -i 4 -n -a -p $GAMESERVPID
> COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
> srcds_lin 18039 hlds7u  IPv4 1132076712  0t0  UDP x.x.x.x:27117
> srcds_lin 18039 hlds8u  IPv4 1132076713  0t0  UDP x.x.x.x:27017
> srcds_lin 18039 hlds9u  IPv4 1132076714  0t0  UDP x.x.x.x:27217
> srcds_lin 18039 hlds   10u  IPv4 1132076715  0t0  TCP x.x.x.x:27117
> (LISTEN)
> srcds_lin 18039 hlds   11u  IPv4 1367389900  0t0  TCP x.x.x.x:26018
>
>
>
> My command specified "-steamport 26017", but 26018 is actually in use.
>
>
>
> My solution for this is to simply space out all servers by odd numbers
> when running multiple servers on the same IP.  So, I've got a server at
> 2xx13, 2xx15, 2xx17, 2xx19, etc
>
> Also note the use of "-strictportbind" above.  This feature was added at
> my request by Valve, who graciously answered my call to do so.  By default,
> the srcds application happily tramples on ports and just assigns itself
> whatever the heck it pleases to have.  When -strictportbind is used, in
> theory, the app is supposed to exit with an error, as any sane and
> reasonable daemon would.
>
> For verification, I nmap my own host and diff the output against the
> previous output and get mailed if differences are found.  That way I know
> if anything is gone amiss.
>
>
>
> Roman Hatsiev wrote:
>
>> 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:
>>
>> +port 29016
>> -steamport 29116
>>
>> Those ports are explicitly open on by firewall, etc.
>>
>> While troubleshooting some other issues (that I think are
>> un-related), I noticed these errors in the logs:
>>
>> WARNING: Port 27005 was unavailable - bound to port 27006 instead
>> WARNING: Port 27020 was unavailable - bound to port 27021 instead
>>
>> What are those ports all about?
>> Is it not using the -steamport parameter?
>> or is this yet more communication of some other form?
>>
>> __**_
>> To unsubscribe, edit your list preferences, or view the list
>> archives, please visit:
>> 
>> https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds
>>
>>
>>
>> __**_
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds
>>
>>
> --
> # Jesse Molina
> # Mail = je...@opendreams.net
> # Cell = 1-602-323-7608
>
>
>
> __**_
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Re: [hlds] SRCDS not honoring -steamport parameter any more?

[Jesse Molina]

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_linux -game tf -ip x.x.x.x +clientport 27017 +hostport 27117 
+tv_port 27217 -steamport 26017 +replay_port 27417 -strictportbind 
-pidfile /path/to/my/server.pid -maxplayers 25 +map cp_dustbowl


Now, here is what lsof said is actually in use:

lsof -i 4 -n -a -p $GAMESERVPID
COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
srcds_lin 18039 hlds7u  IPv4 1132076712  0t0  UDP x.x.x.x:27117
srcds_lin 18039 hlds8u  IPv4 1132076713  0t0  UDP x.x.x.x:27017
srcds_lin 18039 hlds9u  IPv4 1132076714  0t0  UDP x.x.x.x:27217
srcds_lin 18039 hlds   10u  IPv4 1132076715  0t0  TCP x.x.x.x:27117 
(LISTEN)

srcds_lin 18039 hlds   11u  IPv4 1367389900  0t0  TCP x.x.x.x:26018



My command specified "-steamport 26017", but 26018 is actually in use.



My solution for this is to simply space out all servers by odd numbers 
when running multiple servers on the same IP.  So, I've got a server at 
2xx13, 2xx15, 2xx17, 2xx19, etc


Also note the use of "-strictportbind" above.  This feature was added at 
my request by Valve, who graciously answered my call to do so.  By 
default, the srcds application happily tramples on ports and just 
assigns itself whatever the heck it pleases to have.  When 
-strictportbind is used, in theory, the app is supposed to exit with an 
error, as any sane and reasonable daemon would.


For verification, I nmap my own host and diff the output against the 
previous output and get mailed if differences are found.  That way I 
know if anything is gone amiss.




Roman Hatsiev wrote:

These are clientport and tv_port. For some reason srcds uses steamport+1
instead of steamport.

On Oct 31, 2012 8:48 AM, "Weasel" mailto:wea...@weaselslair.com>> 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:

+port 29016
-steamport 29116

Those ports are explicitly open on by firewall, etc.

While troubleshooting some other issues (that I think are
un-related), I noticed these errors in the logs:

WARNING: Port 27005 was unavailable - bound to port 27006 instead
WARNING: Port 27020 was unavailable - bound to port 27021 instead

What are those ports all about?
Is it not using the -steamport parameter?
or is this yet more communication of some other form?

___
To unsubscribe, edit your list preferences, or view the list
archives, please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds



___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds



--
# Jesse Molina
# Mail = je...@opendreams.net
# Cell = 1-602-323-7608



___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Re: [hlds] SRCDS not honoring -steamport parameter any more?

[Roman Hatsiev]

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
recall actual name, but it was broken for as long as I remember.

Also I'm not sure what clientport is for, but srcds uses it anyway so I
prefer to configure it manually to avoid nasty surprises of dynamic port
allocation  with many game servers running on the same box.
On Oct 31, 2012 8:54 PM, "Weasel"  wrote:

> 
>
> 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 for the [client/server]
> > game communication and another for Steam
> > network communication:
> >
> > +port 29016
> > -steamport 29116
>
> Regarding first reply:
> > From: Roman Hatsiev 
> > These are clientport and tv_port.
> > For some reason srcds uses steamport+1
> > instead of steamport.
>
> I would have thought that for any additional client
> port (beyond the port the game runs on, and the
> designated steam communication port) would be
> dynamically assigned - not hard-coded like that.
>
> I would think that "client port" would be the port
> I am specifying the game to run on.  Weird.
>
> Not sure what you mean by "steamport+1"?
> If I set it to 29016 is it using 29017 instead?
> When did that start?
>
> Regarding second reply:
> > From: ics 
> > You have another server eunning that is using
> > those ports.
>
> Actually, NO - at least not intentionally.
> I have 13 games concurrently running on this server,
> and EACH has been explicitly assigned it's own
> unique ports (2 each, 1 for game and 1 for steam).
> In this case, 29016 for the game, and 29116 for Steam.
> Those in-turn are allowed in the firewall (in-bound
> anyway, for  outbound everything is basically allowed
> at the moment).
>
> - Thanks again! [Weasel]
>
> 
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Re: [hlds] SRCDS not honoring -steamport parameter any more?

[Weasel]

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 for the [client/server]
> game communication and another for Steam
> network communication:
>
> +port 29016
> -steamport 29116

Regarding first reply:
> From: Roman Hatsiev 
> These are clientport and tv_port.
> For some reason srcds uses steamport+1
> instead of steamport.

I would have thought that for any additional client
port (beyond the port the game runs on, and the
designated steam communication port) would be
dynamically assigned - not hard-coded like that.

I would think that "client port" would be the port
I am specifying the game to run on.  Weird.

Not sure what you mean by "steamport+1"?
If I set it to 29016 is it using 29017 instead?
When did that start?

Regarding second reply:
> From: ics 
> You have another server eunning that is using
> those ports.

Actually, NO - at least not intentionally.
I have 13 games concurrently running on this server,
and EACH has been explicitly assigned it's own
unique ports (2 each, 1 for game and 1 for steam).
In this case, 29016 for the game, and 29116 for Steam.
Those in-turn are allowed in the firewall (in-bound
anyway, for  outbound everything is basically allowed
at the moment).

- Thanks again! [Weasel]




___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Re: [hlds] SRCDS not honoring -steamport parameter any more?

[ics]

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
> 
> Those ports are explicitly open on by firewall, etc.
> 
> While troubleshooting some other issues (that I think are un-related), I
> noticed these errors in the logs:
> 
> WARNING: Port 27005 was unavailable - bound to port 27006 instead
> WARNING: Port 27020 was unavailable - bound to port 27021 instead
> 
> What are those ports all about?
> Is it not using the -steamport parameter?
> or is this yet more communication of some other form?
> 
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Re: [hlds] SRCDS not honoring -steamport parameter any more?

[Roman Hatsiev]

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:
>
> +port 29016
> -steamport 29116
>
> Those ports are explicitly open on by firewall, etc.
>
> While troubleshooting some other issues (that I think are un-related), I
> noticed these errors in the logs:
>
> WARNING: Port 27005 was unavailable - bound to port 27006 instead
> WARNING: Port 27020 was unavailable - bound to port 27021 instead
>
> What are those ports all about?
> Is it not using the -steamport parameter?
> or is this yet more communication of some other form?
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds