Hear hear! (Is that the right homonym to use here?) Michael - IMO, you hit it right on the head. The VAC2 port binding has great potential for overlap with the main listen port for existing servers, especially for those of us with many servers. All ports that are bound by the srcds/hlds server processes we should be able to explicitly specify.
-Justin On Apr 7, 2005 1:50 PM, Michael McKoy <[EMAIL PROTECTED]> wrote: > > You've missed the point then. Yes. There is no technical reason you can't > put it on port 1000, 55555, 16969, whatever you want. The point is that IN > PRACTICE, most people do NOT do that nor have a desire to do so. They like > to use the default port or a similar port, evidenced by the fact that > there's thousands of servers on ports 27016-27030, etc. > > My point has never been that there is a technical reason you couldn't use > any port you want. My point was simply that most people, though in > particular game server providers, traditionally use ports starting at > 27015 and up. As another person posted to the list, they had over 90 > customers on port 27030. VAC2 has disrupted their business and forced them > to move these customers. > > A bunch of you seem hell bent on bashing me for a bad choice of words in > my first post, which I tried to correct, while ignoring the issue I tried > to get addressed: > > VAC2 binds itself to 0.0.0.0:27030 and there's no way for us to change > that, and it has affected many people's server setups. It should obey the > -ip parameter, and perhaps even a -vac2port parameter. > > > _______________________________________________ > 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
