Fails to block non-Internode AU servers

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have Steam Limiter installed and running before starting Steam.
2. Download some games through Steam. 
3. Observe data sapping out of your account. ;)

What is the expected output? What do you see instead?
I expect all downloads to be unmetered or otherwise fail to download. Instead, 
everything is still downloading, and on average only about 20% of data is 
unmetered (roughly the same as without the limiter).

What version of the product are you using? On what operating system?
0.7.0.3 on Windows 8 Professional

Please provide any additional information below.
- I'm in Australia and my ISP is Internode
- The full list of content that is unmetered on my plan is here: 
http://www.internode.on.net/residential/entertainment/unmetered_content/
- I'm using the default profile, which auto-detected my ISP to be Internode.
- Steam Limiter always runs on start-up.

Original issue reported on code.google.com by Diamond...@gmail.com on 2 Dec 2013 at 10:30

[GoogleCodeExporter]

The usual first step for diagnosing this is to capture a trace of what 
steam-limiter can see Steam trying to do using the DbgView utility from 
SysInternals, at http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

When steam-limiter is loaded into Steam it will print a message saying it was 
loaded in successfully, and from then on as Steam's internal HTTP client goes 
out to webservers, steam-limiter prints every URL that it accesses.

I've attached a sample which I've just taken where I start Steam and download a 
small game; this shows how steam-limiter blocks all the game download URLs 
except for the ones sent to my ISP - in my case, steam.cdn.vodafone.co.nz

If you capture a DbgView trace which shows steam-limiter loading into Steam and 
then the start of a game download, we can see if you see something similar to 
what I get.

It may be that steam-limiter actually is failing to hook into Steam for you, 
for instance due to some other program interfering with it or something like 
that. In that case, if it isn't able to intercept Steam then we should see it 
complaining in the debug output and we can look into why that might be.

Original comment by nigel.bree@gmail.com on 5 Dec 2013 at 3:49

• Added labels: Component-Logic, Performance

Attachments:

• steam-download.log

[GoogleCodeExporter]

I'm also on Internode and tried steam-limiter out and most traffic was also 
metered. Used DbgView and I didn't see the part where the domain resolves to an 
IP and SteamFilter didn't get attached. I tried closing programs that might 
have been causing the issue, but in the end I ran steam-limiter as an 
administrator and that seemed to have did the trick.

Original comment by semba.de...@gmail.com on 27 Feb 2014 at 1:36