Quote:
|
3. Nothing has changed except the Limewire build, and yet I am getting hardly anyone uploading from me.
|
Actually something else has changed too. LimeWire has started to cluster its nodes to shield you from traffic. You are receiving less upload requests from non-limewire hosts. Normally I would assume that limewire users and other gnutella users have the same download behaviour, but maybe this is not the case. In addition upload queues have been introduced and usually, - and if you are in somebody's upload queue you would not try to download from alternate locations as aggressively as you would without upload queues. So maybe this is another reason for the changed number of upload requests. There's nothing wrong with the program at all. (Well, older versions of LimeWire or other gnutella clients that don't support upload queues will not be able to download from you if there are clients in your upload queue).
Quote:
|
4. I *know* something is wrong. It is not a simple matter of forcing the IP as I have had this in place under this version of Limewire and under previous versions.
|
And I guess you did not set up your router for port-forwarding, in which case forcing your IP is completely useless. Nothing's wrong. The network has just changed.
Quote:
|
I have set the Upload Limit to 100 for "number of uploads" from a single user. Despite doing this, I am receiving reports from users who are on, let's be generous and say their 10th upload (not their 100th) of "Upload Limit Reached." They might reach 10 if I leave Limewire on 48-72 hours. Question: Is there a cut-off to the number of uploads allowed per IP if I have set it to 100 and the IP obviously has gotten nowhere close?
|
I would think that LimeWire set your overall upload limit to a lower value than what you set as "max upload slots" value. It does that at times, when it seems you can't sustain that many uploads.