In this thread I will explain the methods used to connect to the WA Steam Server.
STEAMWATCH - DOWNLOAD LINK
As some of you may know, there is the option of using the application known as "SteamWatch" to specify what server/s Steam can connect to. This however is a method that I won't recommend as Steam will still be able to access the other servers (very briefly). This results in Steam leaking some bandwidth because SteamWatch only manages to close the connection to other servers after which some traffic has been transferred/leaked.
Now on a 384Kb/s line the amount of BW leaked wont be too significant, but a 4Mb/s line manages to transfer much more BW before SteamWatch closes the connection. (Usually a few Megabytes at most, definitely not 100s of Megabytes. If so, then you've configured SW incorrectly.)
So the Pros and Cons of using SteamWatch would be:
*Pros -Easy to setup. (Just add the desired Server addresses into the XML file.)
-Can easily be dis or enabled.
-A bunch of servers can easily be added to the XML file.
*Cons -Leaks BW. (Note the amount leaked isn't too concerning even on a 4meg line.)
-The need to install third-party software.
The STEAMWATCH how-to Guide:
1) So first off, make sure that Steam isn't running.
2) You'll then want to download and install SteamWatch. (Installing the Tray Icon simplifies the management of the service.)
3) Before you start editing the settings, make sure that the SteamWatch service isn't running. (Right-Clicking on the Tray Icon and stopping the service should work, but I would advise you to have a look at all the running processes in Task Manager and end the SteamWatch process if necessary.)
4) Then navigate to the installation directory and find the SteamWatchSettings.xml file. Open it with Notepad and replace all the other server entries with the two WA Steam Server addresses. (ONLY THE SERVER ENTRIES)
Namely:
< address> 41.185.60.43 < /address>
< address> 41.185.24.21 < /address>
5) After Editing and Saving the file you may then start the SteamWatch service and launch Steam.
6) Be sure to test if everything is working as it should before you attempt to make a large download by monitoring the servers that Steam is connecting to, hopefully the two WA servers. (I mention this again in my second post)
Here is my SteamWatchSettings.xml File (Just Copy&Paste into the installation directory of SteamWatch if you want.)
----------------------------------------------
FREY STEAM FILTER - (See Xenonification's Thread) (Credit to Xenonification)
----------------------------------------------
FIREWALL
Now the method (and credit to Detritus) that I make use of is by restricting Steam through the means of a firewall.
I've found that by using a firewall to specify what servers Steam may connect to is much more efficient as it doesn't allow Steam to make any other connections on Port 27030 other than the WA server.
From my experiences, instead of Steam trying to connect to other servers when using SW, Steam just simply locks onto the WA server right away and if the content is available, starts to download immediately. Resulting in no BW leaked.
So the Pros and Cons of using a Firewall would be:
*Pros -No BW leaks.
-Much more efficient and hassle free. (When the server is up and running)
-No third-party software needed.
*Cons -Isn't as easy to setup.
-If the WA server is offline, then Steam will fail to log-in.
(You'll then need to disable the firewall, log-in and re-enable the Firewall.)
The options that I'll be able to help you with are ESET and COMODO. (Tried and tested them myself.)
N.B Very Important, The Protocol used is TCP&UDP and the Direction Both (In/Out). And make sure that you apply these settings to the "Steam.exe" file, and not just as general network rules.
* If you've got ESET Smart Security 4, then here's what you need to do.
Apply 3 Rules for Steam.exe
* Allow everything
* Block all traffic to remote port 27030
* Allow traffic to remote port 27030 on the WA Steam Server(41.185.60.43)
In tabular form
* If you've got Comodo Internet Security Premium (Free Anti-Virus/Download), then here's what you need to do.Code:Rule: Action: Direction: Local Port: Remote Host: Remote Port: Allow All Allow Both Any Any Any Block Port 27030 Block Both Any Any 27030 Allow WAGE Steam Server Allow Both Any 41.185.60.43 27030
Similar to the Eset rules, except that Comodo seems to apply firewall rules from top to bottom.
So I have 3 Rules for Steam.exe
* Allow Destination Single IP 41.185.60.43 on Destination Single Port 27030
* Block All IPs on Destination Single Port 27030
* Allow All
(You can try the standalone Comodo Firewall and keep your current AV if you wish, if you've decided to install the Free Comodo AV, then after the instalation you'll need to "Add or Remove Components" from the start menu of Comodo and add the Firewall.)
These settings with a bit of alteration should work for most firewalls, just be sure to go and read up on how the rules in your firewall program are applied.
----------------------------------------------
Games available off Steam via Freezone - Compiled List


Reply With Quote





Bookmarks