Log peer blocking torrent info

[Sindu]

I have a simple request currently (v1.4 build 402) the logger tab shows the IPs of peers blocked by the IP Filter easily as

[time] IpFilter blocked peer x.x.x.x

that is, without recognizing which torrent's swarm that peer referenced to. So when you have so many active torrents at a time there is no method to know which one is referencing blocked IPs. I would like the log to detect the torrent, something as given below :

[time] IpFilter blocked peer x.x.x.x from torrent [name]

A very minor section but since it looks trivial to implement I consider that I would indicate this .

[Jackson2]

If you are running with the DHT and peer exchange on, this may not be possible to consider which torrent an IP references without establishing a connection with that IP and exchanging some information....Which kinda defeats the purpose of blocking this in the primary place if it's absolutely hostile! Any IP address which is in a torrent's IP list (ordered by µTorrent) could definitely be blocked as requested though. I am all for that.

[Sindu]

You have created an interesting point. I am not sure about the details of the peer-to-peer initial handshake, but if it has the torrent hash then it would detect the torrent. And a reply to the restercted peer of "sorry mate, don't have that torrent" shouldn't be a security problem. (I don't know how the IP Filter performs. Does the some other client find a "port unreachable" error, no reply at all, a "don't have that torrent", ...?)

But as I told you that it was a very simple request. If it consumes more coding then I assumed or is easily not practical, please just avoid this . (The developers could use the time improving the cache.

[Techno01]

It would be very useful and as well as in case, if you are running with the DHT , it can be possible without the support of this . When you dl several torrents at the exact time and some of them with small amount of seeds are restricted by ipfilter and you are unable to dl this and you are not sure about why I am running with such a scenario, torrent with one seed being restricted but the torrent is legal so no required for this .

[Suhasini]

It also would be fine if "x.x.x.x" was really peers IP, and not the primary statement from the ipfilter.dat file

[17:11:28] IpFilter blocked peer 0.0.0.0
[17:12:15] IpFilter blocked peer 104.1.0.0
[17:12:22] IpFilter blocked peer 104.1.0.0
[17:13:24] IpFilter blocked peer 0.0.0.0
[17:15:52] IpFilter blocked peer 0.0.0.0
[17:16:56] IpFilter blocked peer 0.0.0.0
[17:16:59] IpFilter blocked peer 104.1.0.0
[17:17:01] IpFilter blocked peer 0.0.0.0
[17:17:25] IpFilter blocked peer 0.0.0.0
[17:17:32] IpFilter blocked peer 0.0.0.0
[17:18:00] IpFilter blocked peer 104.1.0.0
[17:19:19] IpFilter blocked peer 0.0.0.0
[17:20:04] IpFilter blocked peer 104.1.0.0
[17:20:18] IpFilter blocked peer 0.0.0.0

Do you all have any idea about this ?? And even super guess perform would not fix the mistery of this log