What is this?

Sorry, no image.


Slash, do not tell me these are two torrents I have seeded, please.

ok, i won't tell you "these are two torrents you have seeded"... but i will say, first of all, that it is not nice to share someone's ip-addresses like this, right? and second: there's a bunch of reasons for your outcome.

I hope you saw the problem:
The sockets I were connected had different port numbers from those reported by the tracker.
Think why. And don't explain me. Keep it for yourself.

i think, besides the times of unruly-truly wisdom, you're mostly paranoid and seeing plots where they are not... i see no problem with this and consider it to be completely normal, well, at least 100% explainable, but in no way - erroneous.

ps. if this thread was posted solely for my purpose, - you could've pm-ed this to me... keep trying to get me publicly, aren't you? it's ok. =)

Well, you could explain it to me then.
It would be interesting for me to know how a program using one socket only while connected to another sends different socket address in HTTP GET message to third.

P.S. How could I send a file using a PM?

=) you can send file as plain http...link to the file in the pm, or as you did in last forum post - using bb codes, they work fine in pms.

one simple explanation - your soft shows ports you're using on your system to connect. i don't know how vuze (right?) works..

another explanation involves user suddenly finding new leeches not-connectable, and tries to make their client work on a different port, although old peer stays with old port in db.

third - starts as second, although user manages to become connectable on a new port, but old peer still stays in db for some time, possibly being selected as the "proper" one with wrong ports reported.

fourth - one of the clients mainline/bittorrent 6 something something could act that way - connect to each new peer on a range of peers... who knows... there are other reasons, i'd need to see that file and your software again...

I am concerned about so many non-connectable users.

UTorrent and Vuze uses one port only.
Vuze is the perfect software.

The only reason I see is the users, I have shown, were behind a proxy and the tracker determined the IP address by the source address instead by the address sent in the HTTP GET message. If this was a case the proxy could be connectable or not (acctually I don't know).

When those users have connected to me Vuze had their real socket addres.