No uploads after router upgrade - plea for advice
 

Howdy all.

I've recently replaced my USB DSL modem (connected diretcly to my spare PC) with a standalone router/firewall/DSL box (with which the spare PC talks via ethernet). Prior to the upgrade, my local LimeWire install was uploading 2GB/day and the queue was always full. Now it barely uploads 100MB/day and the queue is often empty.

Something's definately broken. I suspect introducing NAT into the equation, but could use advice.

Things I've tried so far:

• Disabling the firewall entirely (it initially was configured to pass all traffic on 6346 and 6348, as per the software firewall in the old setup). No change.
• Configuring NAT to pass *all* ports and protocols to the box running LimeWire rather than just TCP and UDP on 6346 and 6348. No change.
• Toggling the 'force IP' switch in LimeWire options. No change.
• Reverting back to the USB modem. Uploads at 2GB/day and a full upload queue.

If there's anyone out there with happy LimeWire on a home network - in particular using a Solwise 715 modem/router - I'd appreciate both encouragement than it's possible and advice on working setups.

Cheers.

http://www.sciforums.com/f72/s/showt...threadid=27907 has a very long (and currently inconclusive) discussion of a similar problem with a USB cablemodem/router.

I use a home NAT with a linksys router. I give each of my machines a static IP, and map a different port to each. The new Linksys firmware upgrade didn't seem to work well, so I reverted to the December firmware and all is well.

It has been a real problem, though, to get it running well this year. The ISP was also experimenting with p2p controls.

Well, I've spent a week playing with this and have concluded that the hardware and local network config are fine - the only conclusion I can come to is that it's a bug in limewire.

With one PC, one router and no NAT or firewall in the way, LimeWire appears to act is if it's behind a firewall and insists on pushing content to people downloading files from it. Something is confusing the LimeWire mechanism that determines if sockets on the local PC are visible to the outside world.

Happy to provide details to anyone who fancies debugging, but sadly can progress no further myself. In the meantime, I'll be running as a leech.