r00ted Posted January 17, 2006 Report Share Posted January 17, 2006 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 126.96.36.199[11:10:53] IpFilter blocked peer 188.8.131.52[11:15:53] IpFilter blocked peer 184.108.40.206and 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 220.127.116.11But, 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:18.104.22.168:5847122.214.171.124:4567126.96.36.199:6881188.8.131.52:52525[b]184.108.40.206:30000[/b]220.127.116.11:3245918.104.22.168:68822.214.171.124:32459126.96.36.199:688188.8.131.52:688184.108.40.206:44735220.127.116.11:9562192.168.1.1:6553518.104.22.168:68822.214.171.124:49153Also, from what I noticed, ipfilter.dat does not "filter" UDP/DHT packets/connections, is that right? Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.