Introduction:
I'm behind a router.
In order to share I've opened the gnutella port in the router and traffic is redirected to my machine. To broadcast my real IP I have to force my IP address.

First request: the header of -remote-ip in the connection panel has my real address, and LimeWire should use it to respond to queries so Force IP would be of less use.
-I know there has been discussion about that in the mailing lists, and AcquisitionX is doing it well.

Second request: my ISP is changing my IP in a mean of about 1-2 hours. Each time my downloads halt, stalling at 0K until I kill the download and resume it in the library window.
-Possible solution, Limewire should keep in memory the remote IP address and each time a new ultrapeer connection is being made it should use the remote IP address of the last connection made.
-If the new remote IP is different, Limewire should cancel ongoing downloads and restart them by connecting to the uploaders hosts.

Third request: when the remote IP has changed, the outgoing uploads also stall.
-Possible solution: send a result pulse to the downloading hosts so they find your new location and resume their downloads.

With these changes I feel Limewire would be a more robust client and it would benefit to gnutella.

Has anybody other requests LW team should be aware?

Thanx to all