Jump to content

Problems with ipfilter.dat


Toshimo

Recommended Posts

I'm using 3.4.2 and I've created a combination ipfilter.dat out of the last Bluetack non-subscription version and another version from a different site, screening for duplicates.  It's a fairly large filter now and causes uTorrent to load incredibly slow ( >1m to open).  In most locations, this has worked fine, although slow.  At my home pc, though, the logger has no output of any kind after opening.  Is there any way to determine if this is loading properly?

Link to comment
Share on other sites

Can you please try and test this ipfilter:

0.0.0.0 - 79.255.255.254

81.0.0.0 - 255.255.255.254

 

And see if you get only 80.x.x.x peers? It didn't work for me, and it looked like the second line was totally inaffective/unread :(

Link to comment
Share on other sites

  • 1 month later...

At the moment, I no longer see confirmation that the ipfilter.dat file is being loaded in "Logger".  I will try the modified/simplified filter you have suggested and see if there are results.  I"m guessing that any peers outside of the 80.x.x.x subnet means that the filter is no longer working?

 

Between this and the bandwidth limiter no longer working, I'm beginning to suspect the CIA & NSA have infiltrated the uTorrent team (j/k)

 

I may have to roll back to some older version until this stuff clears up...

Link to comment
Share on other sites

>any peers outside of the 80.x.x.x subnet means that the filter is no longer working?

Correct. Looks to me as if this is working OK in the latest 3.4.2 stable.

 

And the bandwidth limiter is working, most of the times (=use cases)...

Link to comment
Share on other sites

By going to the "Peers" tab and selecting Reload IPFilter, I do see the Logger pick this up.  It used to show at the top/beginning of the Logger when I started the app, but I may have too many error messages.  I wish it were possible to archive torrents so that a history/record of previous torrents could be scanned if necessary, but that didn't kick off attempts by the application to restart/reload old torrents.  I suppose 2800 completed torrents over the years might be a bit much for the logger to parse and still have room for the ipfilter message.

 

It's interesting, after grabbing a BitTorrent bundle and getting a huge download speed of about 8MB/s to complete the torrent in less than a minute, I no longer seem to have the problem with upload bandwidth jumping over the limited setting.  I'll keep an eye on it over the next few days.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...