New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)

Mr_B wrote:

I have to ask again, what, exactly, is used to test the port, and gets the answer that it's closed, to make you guys default to thinking that transmission is at fault? At this point nobody can help you since they cant reproduce the error, and quite frankly, the error assumed, and the error messages supposedly being had according to the last few posts, doesn't add up. The communication with the TRACKER has NOTHING to do with the forwarded (or not) port for Transmission. If you can't reach the tracker, the problem isn't the port being forwarded or not. B!

Quite right, and my install of transmission does in fact work fine. The blocklist seemed to be the issue, the mint 7.1 install iso downloaded fine once I turned it off.

However, transmission's preferences page still reports the port being closed. I've verified it's open by ssh'ing to an Amazon EC2 instance I use at work, and using telnet to connect back, using the port listed. It happily connects. Switching uPnP off at the router, rebooting the nas and trying telnet again with the new, randomized port fails. Clearly it's working as intended, just being mis-reported in the preferences window.

Since it does work, I'm not really concerned with fixing it. Merely adding my two-bits to addict, confirming he's not the only one seeing it. Whether that particular issue has anything to do with his other issues, I don't know enough to have an opinion on.