I never said anything about random ports, I said "random" software. If some random software steals a port I need for something else THAT SOMETHING ELSE doesnt work any more... Being down to the last (masterserver) uncontrollable port the issue isnt that great any more. And yes, I could do some more workaround on my non-linux-based firewall.
VAC servers, at least, are really crappy when it comes to replying to VAC requests which will both deny the server secure mode, until the missing response has arrived and it can and is causing spikelags on the servers, which I would like to control better/eliminate. Though the VAC comm. isnt being done over the masterserver port. Writing such a script would be a waste of time, if there is a cmdline option to control it, which is also a lot less ugly. Furthermore it will be a boring script to write since you have to wait for port to be open before you can get it, and it would be yet another workaround script in an already complex setup... mostly due to the steam software. :-( Regards Thomas @ DSRack.com On Fri, 2009-07-10 at 17:08 +0800, Shane Arnold wrote: > Well it isn't random. By your own information it is 26901 +1 per server. > It wouldn't be hard to write a script that automatically writes an > iptables rule for each server started. You have't really stated why you > want to control the port used by VAC communication? I can only assume > it's either to 1) block it or 2) route over a different port. > > _______________________________________________________ > > Shane Arnold - [email protected] > > "For want of a nail, the horseshoe was lost. For want of a horseshoe, the > horse was lost. For want of a horse, the messenger was lost. For want of a > messenger, the message was not delivered. For want of an undelivered message > the war was lost." > > > > Thomas Hjorth wrote: > > Really not an option when it on the server I want control over what > > ports "random" software decides to bind to... I´m not looking for a > > workaround, only if the port can be set like all the other. > > > > Regards Thomas @ DSRack.com > > > > > > On Thu, 2009-07-09 at 21:37 +0800, Shane Arnold wrote: > > > >> Not sure you can set the starting port for the master server comms. If > >> you are trying to control which port master comms traffic goes over you > >> could always try a redirect on your firewall? > >> > >> _______________________________________________________ > >> > >> Shane Arnold - [email protected] > >> > >> "For want of a nail, the horseshoe was lost. For want of a horseshoe, the > >> horse was lost. For want of a horse, the messenger was lost. For want of a > >> messenger, the message was not delivered. For want of an undelivered > >> message the war was lost." > >> > >> > >> > >> Thomas Hjorth wrote: > >> > >>> Hi all > >>> > >>> Does anyone of you guys (and girls :-)) know how to set/control the > >>> (source) port which is used to communication with the master server? > >>> > >>> It seems to always pick 26901 and automatically add 1 to the port for > >>> each server started (without -nomaster). > >>> > >>> I have checked http://forums.srcds.com/viewtopic/8338 without any luck > >>> and for some reason the is and sport option, which doesnt seem have any > >>> influence on any ports whatsoever. It would be nice to have some control > >>> of the VAC port as well though. > >>> > >>> Regards Thomas @ DSRack.com > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > >> > > > > > > _______________________________________________ > > 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 _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
