1.7.2 - Unbanning peers when no banned unbans your IP

[Terryj]

It seems as though by (hidden) default your own IP address is 'banned' in each torrent (presumably so you're not polling yourself all the time), however, if you unban a torrent that has no banned peers 1.7.2 unbans your IP giving rise to firewall warnings - the unbanning of your own IP shows up in the logs. This does not seem to happen if there are banned peers for a particular torrent. I never noticed this on previous versions. Running XP.

TerryJ

[Switeck]

I've added LAN ips to my block list and the problem nearly went away.

[nos_slived]

In other words (since the question will probably come from somebody in 6 months):

10.0.0.0 - 10.255.255.255

172.16.0.0 - 172.31.255.255

192.168.0.0 - 192.168.255.255

[Terryj]

The ipfilter.dat only stops connections coming in - it dosn't stop them going out.

Terryj

[Switeck]

If µTorrent is firewalled, you may never see an ip blocked by µTorrent in the LOGGER window because it never tries ips found in the ipfilter.dat list.

...well, it shouldn't and hasn't from what I've seen.

If you've seen otherwise, then maybe it's a bug -- but it's a very obscure one that's hard to reproduce.

Note that the last ip in the ipfilter.dat list MUST include an ENTER (carriage return) on it or it gets ignored.

[Terryj]

So nobody has been able to explain why, when opening uTorrent I start to get "Single scan from a remote host detected: TCP 192.168.0.3:29403, Registered packet....." [my LAN IP address] error messages from my firewall and my IP address is blocked - I repeat, this is only after uTorrent is opened up - I can spend hours without uTorrent running without these errors. I think the whole lot is tied up and broken - this probably ties up with the original message of this thread. Who can give a reason as to why my own machine is scanning itself- only when uTorrent is running?

Terryj

[Firon]

Because it tries to connect to itself. Why does it matter? Just allow it in your firewall and forget about it.

[Terryj]

Allow what? my IP address? The fact that my work involves connecting to 1xA class, 3xB class and a handfull of C class domains all with dynamic IP's I'd be spending more of my time tracking IP addresses to try and stop a broken piece of software than I would getting on with my work. Don't worry, I'll go back to Azureus untill something is done about it rather than chat to people who are trying to defend broken software rather than trying to explain WHY these things are happening on a new release.

[Firon]

Every client tries to connect to itself. I really don't see why it's such a big deal to you, either.

And you do know that classes don't exist anymore, right? Routing is classless now (and has been for what, 10 years?)

[Terryj]

Turning off UPnP mapping stops the warnings - thanks for all your help!! Funny UPnP mapping didn't give errors on earlier revisions.

Try reading the latest UK Computer Shopper if you don't know about class A/B/C IP structures/domains (unless they've published a 10 year old reprint!!)