First, let me say that the Mirrors product seemed like a reasonable place to put this. If I was wrong, then my apologies. Please reassign. Second, let me say that I don't know for sure that there is anything wrong server-side (it might even be intentional), but the pattern is suspicious. Read on. :) Ok, my client is Azureus on my Windows XP SP2 desktop. Holes are poked in both my (Gentoo) router and Windows Firewall. All other torrents I have tried work fine: I see both local and remote peers, with up- and downloading working on both types. For some reason, though, on Gentoo torrents (everything I've tried on http://torrents.gentoo.org/ which is about eight different files), I see no remote peers (I have waited for quite some time). Is this by design, like only trusted seeders are allowed or something, or is something broken in the tracker, or is it some sort of incompatibility between Azureus on the Gentoo tracker?
There are several torrents, that don't have any downloaders, but each has at least one seeder (our own seeder). I've just tried to download install-x86-universal-2004.3-r1.iso from our tracker and I see leechers and seeders too (I was even uploading some stuff). What torrents did you try? Could you check what you see if you try to download something "popular" (with more seeders/leechers)? If it's still not working, could you show us some log of the network traffic (eg. ethereal log)?
I have tried install-x86-universal-2004.3-r1.iso (thinking it was probably the most popular), and am trying it again right now. I am currently connected to 22 out of 68 peers and 3 out of 24 seeders. I do transfers in both directions, but what I'm saying is that all of the connections are initiated locally (connections are two-way, after all). It follows that these peers are seeing remotely-initiated connections from me, so that is evidence that this is a problem at my end. On the other hand, I don't have this issue with any other torrents I've tried, which is evidence that the problem is not at my end. I'm suspecting some sort of interoperability between the particular tracker software and Azureus (my client).
Seems fine on our end. I'm going to close this due to inactivity. Let us know if this is still a problem when 2005.0 gets released. -Jeffrey
Oh, I still have the problem. Just not sure what to do about it, and it doesn't sting particularly badly. I'd prefer to let my bandwidth be used to help out with Gentoo downloads, but it's not causing me great distress (I leave it running anyways...my end does initiate some connections to other downloaders, so it does *some* of its job).
With the new 2005.0 torrents, I want to add that I still see this problem with the primary torrent server (titmouse), but everything works fine with the secondary "unofficial" server (netdomination). The problem is either server-side or compatibility between the tracker software used on titmouse and Azureus (one of the top clients). As requested in comment #3, I'm reopening this bug to alert you that the problem persists with 2005.0.
*sigh* I found the problem. Typo'd port forward in my firewall. I don't know how many times I looked right at it and didn't see "6681" where it should have been "6881". *blush* :) Closing invalid.
Incidentally, I'm at a loss to explain how I saw green smiley's for other trackers (including the unofficial backup gentoo tracker at netdom).
