# netstat -lnp udp 65520 0 0.0.0.0:27011 0.0.0.0:* 8398/hlds udp 0 0 0.0.0.0:27015 0.0.0.0:* 8398/hlds udp 0 0 0.0.0.0:27016 0.0.0.0:* 18684/hlds udp 0 0 0.0.0.0:27017 0.0.0.0:* 30397/hlds udp 0 0 0.0.0.0:27018 0.0.0.0:* 13343/hlds
with 65520 being the Receive-Q as you can see from the inode, only the first of my servers seem to use that port (as expected) to transport/receive data with the banserver. ----- Original Message ----- From: "Jerry Lundstr�m" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 12, 2002 11:43 AM Subject: RE: [hlds_linux] Ban list data/UDP port 27011 > -----Ursprungligt meddelande----- > Fr�n: john [mailto:[EMAIL PROTECTED]] > Skickat: den 12 september 2002 11:34 > Till: [EMAIL PROTECTED] > �mne: RE: [hlds_linux] Ban list data/UDP port 27011 > > > > On Thu, 12 Sep 2002, Jerry Lundstr�m wrote: > > > So on all machines running more then one server only the first one > > started will get the banlist traffic. > > Nononnonono! In my case it has bound to the one started > second to last. The one with the default ip of eth0 (not an > alias IP), and the one with the default port 27015. > well are you 100% on that? =) one server can have crashed and restarted so the other one got the bind, what i mean is that the first one to get the port binded gets it... not all. _______________________________________________ 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
