My guess is that they want queries to always run through the master server, since its controlling the forks.
Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: > Hi, > > Good guess! It is indeed on 27025! Thanks. > > It still doesn't explain thought why we can't query those other servers at > the gameports their running on. > > Maybe VALVe can shed some light on how this thing works. > > Cheers, > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of localhost > Sent: Sunday, November 09, 2008 2:35 PM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] -fork query issue s > > > Eliminating all the entries relating to the 5 servers you know about, I > think your 6th is listening on 27025 or 27026. > I'm not sure what's going on with the extra ports - it may be related to > htlv going by errors I get trying to start individual servers - but it's > the reason why some people aren't having much luck forking more than about > 5 servers at a time > > On Sun, 9 Nov 2008 14:14:55 +0100, "Saint K." <[EMAIL PROTECTED]> > wrote: >> Hi, >> >> What can we make of this? >> udp 0 0 0.0.0.0:27008 0.0.0.0:* >> 4859/srcds_i486 >> udp 0 0 0.0.0.0:27009 0.0.0.0:* >> 5067/srcds_i486 >> udp 0 0 0.0.0.0:27010 0.0.0.0:* >> 5033/srcds_i486 >> udp 0 0 0.0.0.0:27015 0.0.0.0:* <- L4D server >> 4951/srcds_i486 >> udp 332 0 0.0.0.0:27016 0.0.0.0:* <- L4D server >> 4724/srcds_i486 >> udp 332 0 0.0.0.0:27017 0.0.0.0:* <- L4D server >> 4856/srcds_i486 >> udp 664 0 0.0.0.0:27018 0.0.0.0:* <- L4D server >> 4859/srcds_i486 >> udp 0 0 0.0.0.0:27019 0.0.0.0:* <- L4D server >> 5067/srcds_i486 >> udp 0 0 0.0.0.0:27020 0.0.0.0:* >> 4951/srcds_i486 >> udp 0 0 0.0.0.0:27021 0.0.0.0:* >> 4724/srcds_i486 >> udp 0 0 0.0.0.0:27022 0.0.0.0:* >> 4856/srcds_i486 >> udp 0 0 0.0.0.0:27023 0.0.0.0:* >> 4859/srcds_i486 >> udp 0 0 0.0.0.0:27024 0.0.0.0:* >> 5067/srcds_i486 >> udp 0 428 0.0.0.0:27025 0.0.0.0:* >> 5033/srcds_i486 >> udp 1660 0 0.0.0.0:27026 0.0.0.0:* >> 5033/srcds_i486 >> udp 5312 0 0.0.0.0:26901 0.0.0.0:* >> 4951/srcds_i486 >> udp 2656 0 0.0.0.0:26902 0.0.0.0:* >> 4724/srcds_i486 >> udp 2656 0 0.0.0.0:26903 0.0.0.0:* >> 4856/srcds_i486 >> udp 0 0 0.0.0.0:26904 0.0.0.0:* >> 5067/srcds_i486 >> udp 2988 0 0.0.0.0:26905 0.0.0.0:* >> 4859/srcds_i486 >> udp 2656 0 0.0.0.0:26906 0.0.0.0:* >> 5033/srcds_i486 >> udp 0 0 0.0.0.0:26907 0.0.0.0:* >> 4951/srcds_i486 >> udp 2656 0 0.0.0.0:26908 0.0.0.0:* >> 4951/srcds_i486 >> udp 0 0 0.0.0.0:26909 0.0.0.0:* >> 4724/srcds_i486 >> udp 2656 0 0.0.0.0:26910 0.0.0.0:* >> 4856/srcds_i486 >> udp 0 0 0.0.0.0:26911 0.0.0.0:* >> 5067/srcds_i486 >> udp 2988 0 0.0.0.0:26912 0.0.0.0:* >> 4951/srcds_i486 >> udp 0 0 0.0.0.0:26913 0.0.0.0:* >> 4859/srcds_i486 >> udp 2656 0 0.0.0.0:26914 0.0.0.0:* >> 4856/srcds_i486 >> udp 0 0 0.0.0.0:26915 0.0.0.0:* >> 5033/srcds_i486 >> udp 0 0 0.0.0.0:26917 0.0.0.0:* >> 4856/srcds_i486 >> udp 0 0 0.0.0.0:27005 0.0.0.0:* >> 4951/srcds_i486 >> udp 0 0 0.0.0.0:27006 0.0.0.0:* >> 4724/srcds_i486 >> udp 0 0 0.0.0.0:27007 0.0.0.0:* >> 4856/srcds_i486 >> >> The rest of these ports are a mystery to me. >> >> I'd expect the 6th server to run off 27020, but nothing replies there. I >> don't understand what 27020-27026 is used for either. >> >> Cheers >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of localhost >> Sent: Sunday, November 09, 2008 1:49 PM >> To: Half-Life dedicated Linux server mailing list >> Subject: Re: [hlds_linux] -fork query issue's >> >> >> If you run netstat -nlpu | grep srcds: >> >> (numeric, listening, show programs, UDP) >> >> You should see all the UDP ports your 7 srcds processes are listening on >> (6 >> servers and the master). Each will probably be listening on 3 ports. One >> of them will be the actual game port. >> >> On Sun, 9 Nov 2008 13:12:50 +0100, "Saint K." <[EMAIL PROTECTED]> >> wrote: >>> Hi, >>> >>> On our Linux machine we now use the -fork option to spawn the L4D >> servers. >>> The problem here is we can externally only query port 27015. The servers >>> running on 27016, 27017, 27018 and 27019 don't respond on external >>> query's. >>> >>> The 6th server from the -fork option spawns at a random port, not 27020. >> I >>> can't find which port it runs off, although the CPU load indicates the >> 6th >>> server is also being used. >>> >>> Cheers, >>> >>> >>> _______________________________________________ >>> 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 > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
