RE: [hlds_linux] Ban list data/UDP port 27011
On Thu, 12 Sep 2002, Jerry Lundström wrote: > > -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. Possibly.. but if its first come first serve, that means that 5 other servers came first, and didn't get served. Although the server that did start first originally did crash, and has maybe relinquished the port accordingly, and another server has grabbed it.. but I'm not able to replicate this. In any case, something weird is going on, and only one server appears to get traffic from the banlist.. john ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Ban list data/UDP port 27011
# netstat -lnp udp65520 0 0.0.0.0:27011 0.0.0.0:* 8398/hlds udp0 0 0.0.0.0:27015 0.0.0.0:* 8398/hlds udp0 0 0.0.0.0:27016 0.0.0.0:* 18684/hlds udp0 0 0.0.0.0:27017 0.0.0.0:* 30397/hlds udp0 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
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
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. john ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Ban list data/UDP port 27011
On Wed, 11 Sep 2002, john wrote: > normal: > 22:15:16.239243 cs1.myserver.27011 > 12.129.16.83.27011: udp 16 (DF) > 22:15:16.377202 12.129.16.83.27011 > cs1.myserver.27011: udp 24 > 22:15:37.532450 cs1.myserver.27011 > 12.129.16.83.27011: udp 16 (DF) > 22:15:37.669731 12.129.16.83.27011 > cs1.myserver.27011: udp 24 Replying to yourself is bad habit, but netstat says that 27011 locally is bound to the hlds running on the default ip of the server on 27015. When the server changed map, you see a whole load of tarffic (well 17 packets, and there were 16 players on the server) originating from the local IP. tcpdump'ing all traffic when another server restarts and there is no such similar traffic. Valve, is there something to this thinking? john ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Ban list data/UDP port 27011
PiTaGoRaS wrote: > The port 27011 is opened in the remote machine (the ban list server) not in > your server. I suppose the packets are sent from your 27015 (or whatever > port is your server running) to 27011 of ban server and viceversa. So > shouldn't be problems with that. Curious about this, I decided to look at a netstat output, and found out that this is not true. HLDS indeed binds a listen process to 27011, as witnessed below : udp65280 0 0.0.0.0:27011 0.0.0.0:* udp0 0 64.69.87.220:27015 0.0.0.0:* Two things I notice about this. This first is it's binding to 0.0.0.0, instead of the IP address I've specified in the server command line. Even if I got around the incoming issue by binding to multiple IPs, as I do for my clan server, the binding to 0.0.0.0 negates this for the ban information. Secondly, why is there a recieve queue on this? IIRC, recieve queue only builds up if the kernel has received traffic on that port, but the program isn't paying attention to the socket. Somebody forget to actually get the data from the socket when they were coding this? :) (Mystery of the not-working banlist solved? ;) Aluve, TrIaX ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Ban list data/UDP port 27011
You are right, sorry :/ We will have to wait for a response from valve... - Original Message - From: "Jerry Lundström" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 11, 2002 4:00 PM Subject: RE: [hlds_linux] Ban list data/UDP port 27011 Well thats just it, the server on my side DO open 27011 and listens to it. check your own server (netstat -anpu) and you'll see. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
RE: [hlds_linux] Ban list data/UDP port 27011
Well thats just it, the server on my side DO open 27011 and listens to it. check your own server (netstat -anpu) and you'll see. > -Ursprungligt meddelande- > Från: PiTaGoRaS [mailto:[EMAIL PROTECTED]] > Skickat: den 11 september 2002 15:42 > Till: [EMAIL PROTECTED] > Ämne: Re: [hlds_linux] Ban list data/UDP port 27011 > > > The port 27011 is opened in the remote machine (the ban list > server) not in your server. I suppose the packets are sent > from your 27015 (or whatever port is your server running) to > 27011 of ban server and viceversa. So shouldn't be problems with that. > > PiTaGoRaS > - Original Message - > From: "Jerry Lundström" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, September 11, 2002 10:52 AM > Subject: RE: [hlds_linux] Ban list data/UDP port 27011 > > > As I've gotten no answer to this question yet I'll repost it. > > --- > We're no longer using port 27013 for the ban list. You will > now see traffic > (in/out) on port 27011. This traffic is to/from the ban list > server. Make sure you have this port open in your firewall. > --- > > How does this affect running two hlds on same machine? First > hlds that starts opens 27011 but the second can't, does this > mean that only the first hlds will get ban list updates from VAC? > > > > ___ > 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
Re: [hlds_linux] Ban list data/UDP port 27011
The port 27011 is opened in the remote machine (the ban list server) not in your server. I suppose the packets are sent from your 27015 (or whatever port is your server running) to 27011 of ban server and viceversa. So shouldn't be problems with that. PiTaGoRaS - Original Message - From: "Jerry Lundström" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 11, 2002 10:52 AM Subject: RE: [hlds_linux] Ban list data/UDP port 27011 As I've gotten no answer to this question yet I'll repost it. --- We're no longer using port 27013 for the ban list. You will now see traffic (in/out) on port 27011. This traffic is to/from the ban list server. Make sure you have this port open in your firewall. --- How does this affect running two hlds on same machine? First hlds that starts opens 27011 but the second can't, does this mean that only the first hlds will get ban list updates from VAC? ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
