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" <[email protected]> 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 <[email protected]> > > 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 <[email protected]> > > 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
