Does anyone know if the disabling of A2A_PING is permanent? I use this
protocol in several scripts and programs which no longer work.
I find it odd that "better handling of server queries" means they simply
disabled the one that seemed to be the most abused. If the other query
protocols get
It's a very poor fix, I'm having connection issues to servers on my
client. I'm also finding I'm unable to reject client connections
properly now.
On Fri, Jan 28, 2011 at 6:10 PM, David Parker wrote:
> Hello,
>
> I updated my TF2 server with the optional update, and now it does not respond
> to
Hello,
I updated my TF2 server with the optional update, and now it does not respond
to A2A_PING queries at all. It's running, and it responds to A2S_INFO just
fine. Is this the "fix" for the flood attacks?
Thanks,
Dave
___
To unsubscribe, e
On 21.02.2009 10:00, Thomas Kristensen wrote:
> Have any of you seen the same thing happens and is it a LAN only problem?
>
Perhaps I got ahead of myself: I just re-checked and the hostname and
map name updates after map change, although the hostname does not update
after you change the cv
On 21.02.2009 10:00, Thomas Kristensen wrote:
> Have any of you seen the same thing happens and is it a LAN only problem?
>
It happens to internet servers too (at least on my servers) - haven't
found a way to fix it (except restarting the server with correct hostname).
Taavi
__
Hello guys
I got a strange problem. I got a few servers at a LAN party and the problems
is that, when we update the hostname and change map (Adminbot system) the
query from the server still reports the old hostname and map from the start
up. It seems that the query protocol doesn't have any con
6 matches
Mail list logo
