On 02.05.2012 22:12, Peter Reinhold wrote:
For anyone interested, I resolved this issue (and it had nothing to do
with Valves backend update, just some really unfortunate timing that led
me to believe that).
Case is, I am running my servers on ESXi5, and all virtual machines
were using the VMXNet3 type virtual ethernet adapter, on Centos 5.8/64
bit.
Apparantly, the latest iptables on CentOS (1.3.5), in a combination
with the VMWare VMXNet3 drivers (VMWare tools), breaks something, so
that A2S:Player queries just fails silently, leading to L4D/2 servers
not being able to use lobbies, and stats and the like for TF2 to break
as well.
Selecting the e1000 adapter type instead resolved the problem.
Just for future reference if anyone is so unlucky as to run into this
very specific issue :)
On 02.05.2012 14:14, ics wrote:
I get this
#05:Connection to Steam servers successful.
#05: VAC secure mode is activated.
for all forks, and they are the only Source servers (or game servers
at all), running on that specific IP.
As I mentioned, I can connect to the server if I set
sv_allow_lobby_connect_only to 0.
Also, it seems like I can connect when its set to 1, it tries to
reserve a lobby, but then just times out. (I've posted a log of this
in a pastebin a couple of days ago)
I also tried installing a completely fresh L4D2 install, no
meta/sourcemod, and it still does not work.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
