I don't know if/when we'll have a better solution than HTTP proxy for controlling the public IP for websockets. However, in the meantime, -udpforce on the command line should work. Can you please confirm that it does?
I'm sure we'll make sure there is a reasonable solution for multihomed servers. From: Csgo_servers [mailto:csgo_servers-boun...@list.valvesoftware.com] On Behalf Of John Sent: Friday, August 11, 2017 11:36 AM To: csgo_servers@list.valvesoftware.com Subject: Re: [Csgo_servers] Compatibility test for incoming change On 8/11/2017 11:02 AM, Fletcher Dunn wrote: There is currently no mechanism to control what local IP or port this connection is bound to. ... (The master server may refuse to list your server if the public IP used to talk to Steam does not match the IP you are advertising for game traffic.) This would make the new mechanism incompatible with our systems, because all machines here have multiple IP addresses. Some other games have this same design flaw, including some Valve games on Linux (at least, historically). As Kyle does, we have a firewall rule in place on Linux that drops TCP connections to 27017:27019 on the outbound as a workaround for this (forcing a fallback to UDP mode). Before the official release, or at least before you phase out -udpforce, you should modify the software to do a bind() call before connect(), using the IP address specified on the command line. -John
_______________________________________________ Csgo_servers mailing list Csgo_servers@list.valvesoftware.com https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
