>> Taking into consideration that in practice, people aren't going to put >> a CSS server on port 8000 or 43000. In general, most people cluster >> around 27015 and up. The way things are now, you only have up to 27019 >> before you run into the 27020 port from the first server on 27015. >> (And at that point, ports 27021 to 27024 are also in use) > > There's no reason I can't put my game servers on arbitrary ports above > 1024, even with a wealth of non-game services running. A CS server runs > perfectly fine on port 12345 and 54321. (I'm assuming the client, > server, and master server programs aren't broken in some way that > prevents them from doing what any other program can do.)
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
