Yes, but if you sync'd to the update you might need to put the beta binaries back.
-Eric -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sent: Wednesday, November 21, 2012 5:44 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Potential fix for problems on multi-honed servers After this optional update just released, can we still use this beta binary? Thanks in advance. On Wed, Nov 21, 2012 at 2:45 PM, Jason <[email protected]> wrote: > Does this mean if there's an update, will this "fix" be updated in > these zip files or will they potentially be integrated into the > non-beta binaries? > > > On Wed, Nov 21, 2012 at 2:41 PM, Saint K. <[email protected]>wrote: > >> Thanks, updated the servers! >> ________________________________________ >> From: [email protected] [ >> [email protected]] On Behalf Of Fletcher Dunn >> [ [email protected]] >> Sent: 21 November 2012 20:12 >> To: Half-Life dedicated Linux server mailing list ( >> [email protected]); Half-Life dedicated Win32 server >> mailing list ([email protected]) >> Subject: [hlds_linux] Potential fix for problems on multi-honed >> servers >> >> If you are running a multi-honed server, and your server occasionally >> drops out of the master server listing, or appears on the wrong >> public IP, then you may be interested in testing our some beta >> binaries that might fix the problem. The problem begins with a >> disruption while talking on UDP (often during the weekly prop of >> Steam). The Steam client layer then enters a fallback pattern of >> TCP, then UDP, etc. Eventually the disruption is resolved, and it >> can be random whether your server managed to connect to Steam on TCP >> or UDP, depending on where it was in the retry pattern. The problem >> with TCP for multi-honed servers is that it will always bind to the >> default interface, disregarding any request to bind to a particular >> interface. This can cause Steam to see your server as coming from >> the wrong public IP. Depending on your routing rules, NAT, etc, your >> server can drop off of the server browser because clients cannot get to you >> when they send packets to that IP. >> >> Some server operators have worked around this bug with firewall rules >> preventing the server from connecting to Steam via TCP. >> >> These binaries disable TCP fallback for dedicated servers. >> >> http://media.steampowered.com/apps/440/steam_bins_windows_1586041.zip >> http://media.steampowered.com/apps/440/steam_bins_linux_1586041.zip >> >> Be warned that they have not been widely tested. You should only try >> out these binaries if you think you are having problems related to >> multi-honed machines. >> >> Also, note that if you do use these binaries, and then update your >> server, they will probably be reverted. >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list >> archives, please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list >> archives, please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux >> > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
