[observation] ipfilter.dat doesn't block trackers?

[r00ted]

I dont know if this could/should be classified as a bug or not, more of an observation lol.

I just noticed 3 lines in my logger,

[11:04:53]  IpFilter blocked peer 64.27.0.66
[11:10:53]  IpFilter blocked peer 64.27.0.66
[11:15:53]  IpFilter blocked peer 64.27.0.66

and well, turns out that IP actually belongs (it resolves) to one of the trackers' torrents which I have loaded/downloading in µtorrent.

tracker.revision3.com:20000 is the tracker, which resolves to 64.27.0.66

But, I actually finished that download, and am seeding. and so, apparantly µtorrent allowed me to connect to the "tracker", but won't let the tracker send me data?

But every 5 minutes or so (well, look at the time stamp ) it's noting that IP address as being blocked.

Is this normal, that I was even able to 'connect' to the tracker? Tracker status shows as "working" and all

So, I guess, perhaps maybe tracker.revision3.com has some web-based Bittorrent client loaded, to keep their BT releases seeded even after/if everyone leaves?

Copy Peerlist entries:

69.210.62.252:58471
139.57.210.229:4567
24.2.245.153:6881
207.255.89.88:52525
[b]64.27.0.66:30000[/b]
66.41.33.44:32459
68.83.59.159:6881
24.20.253.102:32459
68.68.83.51:6881
68.82.254.51:6881
66.92.129.168:44735
81.224.251.241:9562
192.168.1.1:65535
24.152.199.46:6881
68.151.101.158:49153

Also, from what I noticed, ipfilter.dat does not "filter" UDP/DHT packets/connections, is that right?

[Firon]

Yes, it only applies to peer connections, not trackers or DHT.