On 25/08/2012 10:53, Kyle Sanderson wrote:
There's a known problem with Source 2009 where if you lose your TCP
connection to Steam, there's a good chance your server will become
delisted from the master. The problem stems from Steam reconnecting
using a 'random' machine address instead of the selected ip address
used at server launch. This causes servers to become delisted, and
disappear from the master. While I know the issue has been brought up
a number of times on the list, does anyone have a work around for
this? This is present in both CS:S and CS:GO.
It depends what your configuration is.
Presumably you're saying that the +ip parameter is ignored during this
reconnect and so the new TCP socket is created with "0.0.0.0:27015"
locally and that goes out via the default route / interface and ip to
Valve's master server(s) ?
The most obvious workaround might be using different ports for different
server instances rather than different IP addresses. (I assume they
don't lose the port information with the same bug?) Assuming there is no
specific restrictions on ports you can use, you should still be able to
have thousands of servers.
But there must be multiple ways, using linux, (either by using virtual
interfaces and / or routing or iptables rules) such that a particular
instance of TF2 uses a NIC (real or virtual) that only has one IP
address assigned to it, so that it doesn't need the +ip parameter
setting in the first place - and such that that outbound traffic goes
via the right IP address.
I think what would work or the best way to configure it would depend
upon what you have configured now.
--
Dan
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
