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 : udp 65280 0 0.0.0.0:27011 0.0.0.0:* udp 0 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
