Hello Everyone,

There's an issue that's been bother us for a while that when our TF2
servers reconnect to Steam the steamclient library will reconnect using
TCP. For whatever reason the Public IP detection over TCP is wrong as it
reports the default route. I've verified that the ClientLogon and
ClientGamesPlayedWithBlob steam messages contain the correct game server IP
address, but Steam will auto-correct the connected game server IP on its
end in ClientPersonaState, making it appear as if a player is connected to
a different IP address.

This issue is easily reproduced by specifying the -tcp option when
launching srcds, which will tell steamclient to connect over TCP. When you
type status it will report the default IP address regardless of the setting
of -ip.

As a temporary mitigation you can disable TCP steam connections by blocking
outbound TCP to 27017, 27018, and 27019, and hopefully steamclient will
revert back to UDP.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Reply via email to