The order of the convars (+) is important. Place the +map last. +map will trigger the network to initialize and start the game. So you need to specify all the port convars first. Order of the options (-) is not important as far as I know. We typically just look for the existence of these rather than executing them in the order they appear, which is what happens to the convars.
This is how I start up our servers. srcds_run -game tf -steamport 27704 +exec server/server15.cfg +map plr_pipeline The server/server15.cfg looks pretty much like what I had in my original e-mail. clientport 26019 hostport 27029 tv_port 28034 But you are right about the steam port always being one higher. M. -----Original Message----- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Jesse Molina Sent: Wednesday, July 14, 2010 3:49 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Bind Client port- Linux Hi Milton Your mail below was very informative, but I tested this and observed some discrepancies. For the -steamport argument, the port seems to be whatever you specify +1. For example: On the command line I had; -steamport 26011 What netstat says is actually in use; 26012 I tried other combinations and it was the same. Always the port is incremented by 1. This causes obvious problems. Fortunately, even Valve keeps the default on this one in the 26000 range, rather than the 27000 range, so this isn't too likely to be an issue as long as it won't trample on itself -- I've not actually tried that yet. FYI, the game I am using is TF2. I don't know if other games might use other ports for this. The default here seems to be udp 26901. FYI, this is the last port to appear and won't show up until the server has fully loaded and the line, "VAC secure mode is activated.", appears. Finally, loading the info via "+exec server01.cfg, per your recommendation, did not work at all. The default ports were used anyway. I tried a seperate config file and the main server.cfg file. For my testing, I started the server manually like so; sudo -u hldsuser $SRCDSDIR/srcds_run -game tf +map ctf_doublecross -ip 0.0.0.0 +clientport 27099 +hostport 27199 +tv_port 27299 -steamport 26098 -norestart -pidfile $HLDSHOME/server.pid +clientport +hostport and +tv_port appeared to work as you described. Milton Ngan wrote: > You can control the client, host and tv port using convars on the command > line. > > +clientport<portnum> > +hostport<portnum> > +tv_port<portnum> > > (or alternately placing these into a config file that is refernced via +exec > on the command line) > > Steam also uses a port that will auto-increment, but this is controlled from > the command line option: -steamport > > e.g > > srcds_run -game cstrike +clientport 27005 +hostport 27015 +tv_port 27020 > -steamport 26001 > > or > > srcds_run -game cstrike +exec server01.cfg -steamport 26001 > > server01.cfg: > clientport 27005 > hostport 27015 > tv_port 27020 > > > We do this a lot with left4dead servers in forked mode. The ports numbers are > too close to one another to run a lot of instances before they overlap, which > causes problems. > > > > -----Original Message----- > From: hlds_linux-boun...@list.valvesoftware.com > [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Daniel Vogel > Sent: Monday, July 12, 2010 8:30 AM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] Bind Client port- Linux > > I'm sure he means this: > Network: IP ???.???.???.???, mode MP, dedicated Yes, ports 28001 SV / 27006 CL > the "27006 CL" part. > I'm interested in that too, since I can see the ports counting up > every time I start a new server on the machine, but I'd rather want > them to be in the 28xxx range as well. > > On 12 July 2010 16:08, David A. Parker<dpar...@utica.edu> wrote: >> You mean the port that a client connects to? You just use -port to specify >> that. The default it 27015 (UDP). >> >> Michael K. Gosvig wrote: >>> >>> Hi all. >>> >>> >>> Can any of you guys tell me if there is a way to bind the Client port on >>> Linux Source servers. We have been trying "-clintport XXXXX", >>> >>> But the server still seems to take a random port each time. >>> >>> Michael >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >>> >> >> -- >> >> Dave Parker >> Systems Administrator >> Utica College >> Integrated Information Technology Services >> (315) 792-3229 >> Registered Linux User #408177 >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > > > -- # Jesse Molina # Mail = je...@opendreams.net # Page = page-je...@opendreams.net # Cell = 1.602.323.7608 # Web = http://www.opendreams.net/jesse/ _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
