Log Blocked Connections Option Does Not Work

[sy8]

I recently updated uTorrent to the most recent version, 2.0.2, and updated my ipfilter list from Blocklist (June 1, 2010 version).

Just to make it clear with everyone:

1) I double-checked the Preferences menu to make sure that the ipfilter is enabled and the value is set to true.

2) the ipfilter file is in the correct folder, i.e. Application/uTorrent.

3) under the Logger tab's Peer Traffic Logging, I checked the "Log Blocked Connections."

The problem is that the logger does not log blocked connections anymore. I know that the ipfilter is working because the log does record that ipfilter.dat has been loaded with X entries. Usually after the next line ("starting diagnostic thread"), the log would list all of the blocked connections. However, it has stopped doing so.

I have reinstalled the program and re-downloaded the ipfilter file, but the logger still refuses to log blocked connections.

Does this mean that my computer isn't being protected, or does the latest version of Utorrent no longer log the blocked connections? Am I doing something wrong?

I would greatly appreciate any help. (If you're wondering, I'm running XP on my computer).

Thank you so much!

[DreadWingKnight]

Outgoing connections that match an ipfilter aren't even attempted at all, so they can't be logged as blocked because of this.

[sy8]

Thank you for your fast reply!

However, I'm not sure I understand what you mean as I'm not too computer savvy. Just a few days ago, before I updated the program, I watched the logger record all of the connections that the ipfilter blocked. I mean, the list would literally grow every second. Now, the log is completely blank. If you mean that the ipfilter does not record blocked outgoing connections from my computer to others, I understand that. However, I thought that the log recorded incoming connections from other computers that the ipfilter blocked. Am I wrong?

[Fry]

The problem is that the logger does not log blocked connections anymore. I know that the ipfilter is working because the log does record that ipfilter.dat has been loaded with X entries. Usually after the next line ("starting diagnostic thread"), the log would list all of the blocked connections. However, it has stopped doing so.

That's a perfect description of the same problem I have. I too checked out the settings (although utorrent always did log the blocked connections in earlier versions with the same settings) and there's no reason it shouldn't log, but still it doesn't. The only difference to the original poster (in my case) is, that I'm using Windows 7 x64 and not Windows XP.

I can add one more detail to the situation: Sometimes I use a VPN connection, whenever the VPN is active, utorrent IS logging the blocked connections. It immediately stops, when I disconnect the VPN. This is really weird.

I wouldn't even ask, if this behavior wasn't confusing me, because I too want to know, that the ipfilter.dat is still (always) doing it's job, even when there's nothing displayed.

[Switeck]

Ok, this is a longshot+guess...but maybe uTorrent is binding to a network device even if it's a virtual one created by a VPN. Once the VPN goes down, ipfilter.dat won't filter connections because it doesn't see them passing over the now-missing/dead virtual network device.

[Fry]

That's a good idea. but I don't think that's it. This behavior started before I even had this VPN connection. I only noticed that utorrent logged again once I started using it and only when it was active. So I find it unlikely that binding is involved.

Maybe I'm mistaking something - binding should only work, when it's configured in the client, right? Also, wouldn't utorrent stop working altogether if it was depending on the VPN connection (works otherwise fine without it)?

I wonder if there are even more people, who experience this.

[Switeck]

In my tests, I've discovered a possible bug with ipfilter.dat ip ranges.

If you add another ip that happens to fall inside of an existing ip range, then part/much/all of the existing ip range is no longer blocked.

I've only done this test twice, so I'm still calling it only a possible bug.

[Fry]

I've found several topics here, where people have the same issue, for example:

http://forum.utorrent.com/viewtopic.php?id=51232

http://forum.utorrent.com/viewtopic.php?id=76410

In one of them (not among the two links, didn't have time to locate it again) Firon is answering and saying, that using ipfilters won't help/protect anyway - maybe that's why it still exists, because it isn't perceived as a real problem?

Thanks for trying to help Switeck. I'm gonna keep updating to current versions as they are released and maybe it'll be fixed one day. It's kinda soothing me, that many people seem to have the same bug, so I can at least be sure it's not necessarily my machine.

[Switeck]

Firon was saying blocking ips doesn't work because you can't block who those ips connect to...besides yourself. ips connect to tracker, tracker gives them your ip. Or ips you don't have blocked gives them your ip.