Genuine Behaviour?

[µtorrent-Guest]

Situation:

µT version 1.5 standard port (according to client tab info) is blocked by ipfilter.dat in µT 1.5.1b460.

Question:

is this kind of trying to reconnecting behaviour the normal behaviour of a genuine µT 1.5?

...

[12:28:00] IpFilter blocked peer 68.8.85.217

[12:29:42] IpFilter blocked peer 68.8.85.217

[12:30:36] IpFilter blocked peer 68.8.85.217

[12:31:44] IpFilter blocked peer 68.8.85.217

[12:33:11] IpFilter blocked peer 68.8.85.217

[12:35:20] IpFilter blocked peer 68.8.85.217

[12:37:52] IpFilter blocked peer 68.8.85.217

[12:39:14] IpFilter blocked peer 68.8.85.217

[12:41:26] IpFilter blocked peer 68.8.85.217

[12:42:44] IpFilter blocked peer 68.8.85.217

[12:44:02] IpFilter blocked peer 68.8.85.217

[12:46:09] IpFilter blocked peer 68.8.85.217

[12:48:22] IpFilter blocked peer 68.8.85.217

[12:49:29] IpFilter blocked peer 68.8.85.217

[12:50:15] IpFilter blocked peer 68.8.85.217

[12:51:40] IpFilter blocked peer 68.8.85.217

[12:53:05] IpFilter blocked peer 68.8.85.217

[12:55:11] IpFilter blocked peer 68.8.85.217

[12:57:39] IpFilter blocked peer 68.8.85.217

[12:59:46] IpFilter blocked peer 68.8.85.217

...

[Firon]

Probably an incoming connection.

[µtorrent-Guest]

Yes of course it's an incomming connection.

"It" wants to reconnect to me.

This peer acted very abusive to the swarm and my question is targeted to determin if it is a genuine µT behaviour so the strange abusive behaviour might be only to idiotic settings of the user or if this reconnection atemps might be another indicator that its either a hacked µT or a fake labeled BitVomit client

Situation was/is: 1 seeder, lets say 25 peers, 24 of them including me (and even the fast .SE guys) for days in the 40% while this one "µT" slow but steadily reaches 60..65...70... Sending at least to me keep alive messages, taking what he can but gives NOTHING back (absolutely no other peer rises).

Fortunately the seeder (azureus with hiding seeder status) uses at some point an SE. peer and me as recievers so the swarm then starts rising in its total again.

So if this try to reconnect behaviour is NORMAL and his refusal to play fair to the swarm is just a result of stupid valuesettings by User then i can unblock him again when THIS torrent is thru.

Otherwise maybe this guy is indeed intentionaly hostile[hacked version?] and should stay on my ~10 entry blocklist.

[bleh]

Actually, had it been Bitcomet, it would have thrown you requests at this type of intervals, it used to happen alot when I was banning bitcomet clients who were abusing my upload speeds.

(I tend to like my speeds somewhat evenly distributed throughout the swarm)

Perhaps it's a new permutation of a hacked bitcomet?

[Switeck]

The behavior described here sounds very similar to what was posted here:

http://forum.utorrent.com/viewtopic.php?id=5181

...possibly a hacked client with a faked client id, as not even all BitComet clients are that bad!