1.7 b1355: uT keeps connecting to itself

[tkittich]

from Logger when Log Errors is chosen: (my own ip is 192.168.1.106)

[09:55:16] 192.168.1.106 : Disconnect: Same ID

[09:55:16] 192.168.1.106 : Disconnect: Same ID

[09:55:16] 192.168.1.106 : Disconnect: Connection closed

[09:55:16] 192.168.1.106 : Disconnect: Connection closed

[09:55:22] 192.168.1.106 : Disconnect: Same ID

[09:55:22] 192.168.1.106 : Disconnect: Connection closed

[09:55:24] 124.120.220.244 : Disconnect: Incoming legacy not allowed

[09:55:24] 192.168.1.106 : Disconnect: Same ID

[09:55:24] 192.168.1.106 : Disconnect: Connection closed

[DreadWingKnight]

This happens with the rest of us as well.

The bulk of the issue comes from trackers that give you your own connection info in announce replies.

The rest of the issue comes from DHT replies that include your own connection info.

This issue isn't restricted to uT

[Switeck]

I think part of this problem has to do with having a router. You end up with both a LAN (local) and WAN (internet) ip that can and often DOES end up in the peer ip list collected by µTorrent.

My simple brute-force solution: add BOTH your LAN and WAN ip to your ipfilter.dat file.

I expected to see LOTS of blocks in logger, but actually none occured...since only your computer can create these connection attempts and doesn't try any ips in the ipfilter.dat.

This suggests that µTorrent still has the LAN ip pollution of peer ip lists that was horrifically bad on the FastTrack network!

As a feature request, it should be optional to block all LAN ip requests and never log them in the peer ip lists. Either disabled by default, or maybe ask the user if they have a router but nobody else at their house/on their network uses file-sharing. Or...if in the 10.x.x.x block, attempt to connect to others with a 10.x.x.x address but not anyone in the 192.168.x.x address.