83.142.82.2, eh? I'm in Austria, so this is a server I get sent to quite often. Recently, I had problems with 83.142.82.2 and .7. I've filed a support ticket about them and once it was answered, .7 was up and running again (ping and stuff too) but .2 was still ignoring me completely (be it a SYN to TCP port 27030 or an ICMP echo [= ping]) and it still is doing so now.
This leads us to two possibilities: 1. 83.142.82.2 is doing filtering of both TCP and ICMP echoes (which means that if you're not on the "allowed" list, you won't get answers to ping... which is bad. I doubt you can pull of a DoS using ping and network diagnosis possibilities are a Good Thing™). In that case, the filtering is done wrong, since I get elected for .2 and the server doesn't let me in. 2. 83.142.82.2 is simply down. In this case, I'd beg the person responsible for content servers to try diagnosing the problem or calling CS-Arena to give the box a cold start. Anyway, good that this is getting some mailing list coverage. I find the support site kind of... too impersonal. ~~ Ondra P.S. Drop me a line if I should try pinging or connecting to .2 for diagnostic purposes. Timo Hilbertz wrote:
hi valve, again, our steam content server is not correctly handled by the SCS network. when i set up a fresh steam game servers and use "PreferredContentServerIDs = 10,10,10" in the Steam.cfg file, the steam update is requested from 83-142-82-2.cs-arena.com which is a filtered server so this request will end in a timeout: ./steam -command update -game "Counter-Strike Source" -dir . Checking bootstrapper version ... Getting version 18 of Steam HLDS Update Tool No Steam Content Servers available, please try again later We already had this problem in September and now history repeats itself. I'm really sick and tired of requesting support for our content server that basically reduces the bandwidth load on your network and i wonder why a company like valve seems to be unable to fix such a simple problem. As a matter of fact, we are currently unable to update our steam servers as all requests run into pseudo-firewalled content servers from cs-arena (basically, request are not blocked as they should, the are kept in SYN SENT state and wait until their own timeout limit terminates them). To Do for Valve (especially Mike Dunkle): 1. tell cs-arena.com to properly block their content servers 2. check content server id #10 if this is set to 80.190.65.199, 80.190.65.200 or 80.190.65.201 (we accept connections on all three IPs). Hopefully, this is the end of a never ending story. If not, we will shut down the steam content server, it makes no sense to run a dual opteron with 8 GB RAM that simply does nothing. regards timo
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
