NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)
This is a newly compiled version for the Duo straight from source. It has been configured with "--disable-nls --enable-lightweight --enable-utp" and the default web interface port of 9091.
If it doesn't work after installation, try rebooting.
Not sure if it can be install over the top of super-poussin's version, but if you are planning on uninstalling super-poussin's version then remember to save the torrent files somewhere else first.
To quote myself:
Thanks to super-poussin for the original Transmission add-ons.
Enjoy!
Transmission_2.73.bin - http://www.mediafire.com/?ajpyyc7ujv54o37 no-utp
Transmission_2.75.bin - http://www.mediafire.com/?gbmbhu3hrabf9fe
Transmission_2.76.bin - http://www.mediafire.com/?389i53w9w9rtosm
Transmission_2.77.bin - http://www.mediafire.com/?pm420vuajaim9bz
Transmission_2.80.bin* - http://www.mediafire.com/?5s7dag8ko72doj1
Transmission_2.81.bin* - http://www.mediafire.com/?x4pvvidrgb36df2
Transmission_2.82.bin* - http://www.mediafire.com/?rbctsdae000zoav
Transmission_2.83.bin* - http://www.mediafire.com/?31iul25i0t12qda
Transmission_2.84.bin* - http://www.mediafire.com/?rh5fge4mc8ahzw4
*if the "Upload" button doesn't work or the "Destination folder" field is blank, reload the webpage.
If it doesn't work after installation, try rebooting.
Not sure if it can be install over the top of super-poussin's version, but if you are planning on uninstalling super-poussin's version then remember to save the torrent files somewhere else first.
To quote myself:
tarobun wrote: It looks like upgrading from Transmission 2.42 to this Transmission add-on is a no-no. Sounds like there are conflicting configuration that screws up both installs. :( (eg. /c/addons-config)
It seems the best approach is to fully uninstall the old, delete the config directory, and then install this add-on. Once you're on this add-on, updating is straightforward and can be done over the existing version.
Just a fyi - the default download dir is /var/local/Downloads and there is no username and password with this add-on. If you are prompted for them then the old version was not fully uninstalled.
Thanks to super-poussin for the original Transmission add-ons.
Enjoy!
Transmission_2.73.bin - http://www.mediafire.com/?ajpyyc7ujv54o37 no-utp
Transmission_2.75.bin - http://www.mediafire.com/?gbmbhu3hrabf9fe
Transmission_2.76.bin - http://www.mediafire.com/?389i53w9w9rtosm
Transmission_2.77.bin - http://www.mediafire.com/?pm420vuajaim9bz
Transmission_2.80.bin* - http://www.mediafire.com/?5s7dag8ko72doj1
Transmission_2.81.bin* - http://www.mediafire.com/?x4pvvidrgb36df2
Transmission_2.82.bin* - http://www.mediafire.com/?rbctsdae000zoav
Transmission_2.83.bin* - http://www.mediafire.com/?31iul25i0t12qda
Transmission_2.84.bin* - http://www.mediafire.com/?rh5fge4mc8ahzw4
*if the "Upload" button doesn't work or the "Destination folder" field is blank, reload the webpage.
159 Replies
Replies have been turned off for this discussion
- 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! - Another idea.
You can't use blacklists with some trackers. Or put it this way, blocklists are getting too greedy. 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.- Have you tried clearing your web browser cache, closing your web browser, then reopening Transmission's preference page and seeing if it's then displayed correctly?
It never worked for me, for reasons unknown, but the port is wide open, and the traffic passes through it with no issues. It's just broken. Which is why i was asking what gave everyone the testresults that the port actually was closed, and not just misreported.mdgm wrote: Have you tried clearing your web browser cache, closing your web browser, then reopening Transmission's preference page and seeing if it's then displayed correctly?
B!- Did you ever manually edit the config? If so, did you make sure to edit it using an appropriate text editor.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
