NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
super_poussin
May 17, 2010Virtuoso
New Transmission add-on thread
The previous thread was very long
time to open a new one and prepare the 2.0 :)
time to open a new one and prepare the 2.0 :)
920 Replies
Replies have been turned off for this discussion
- Mr_BGuideI'm guessing i'll look ashamed when i read the answer, but, explain it to me as if i was stupid, how, n' where do i edit "/addons-config/Transmission/transmission-daemon/settings.json file" ?
I'm just assuming here, but since the file isn't visual "all the time" (at least, i don't find it, did i look in the wrong area?) i'm guessing i have to SSH in to the box, and find it there. Guess that means installing the SSH add-on, figuring out where the SSH port is, and what user it has set. Password is supposedly the same as the Frontview one, so i think i know that one. Should figure out how to change it, while changing the Transmission password. So far it's just the password that is eluding me, perhaps as i havent even started using transmission yet...
Does anyone have an opinion as to how well the NAS, running Transmission, plays with private trackers? And do's n' don't i should be aware of?
Thank you for your time.
B! - JarnoGGuideThe addons-config folder is a share, so the easiest way to get there is by browsing to your NAS using CIFS and the admin account (the one you use to log into Frontview). After that you can look up the settings.json file at the location mentioned. The addons-config folder isn't visible is you log in with CIFS using a guest account (if you give no credentials).
I'm using Transmission to download from private trackers and it's working fine with me. The only "problem" i see is that it doesn't show the total amount of seeds/peers when i'm using private trackers, it has no problem connecting to them though. It does show the total amount of seeds/peers when i'm using a public tracker. - Mr_BGuideGuess i'm doing something wrong, when ever i try to connect to that share i get a popup asking for user / pass, but the user is preselected, and cant be changed, set to Readynas\Guest, with no working password. Well, none that i know at least. I got to get going, i've spent half an hour trying to figure this out with the help of Google, but so far no luck. I'll poke it with a bigger stick when i get home tonight.
B! - Davidoff007AspirantIs there somebody out here who can help fix the permissions?
I have made my own share called Torrent
Cifs - guestacces
HTTPS - user nobody
This are my settings.json :
{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": true,
"blocklist-url": "http://list.iblocklist.com/?list=bt_level1",
"cache-size-mb": 200,
"dht-enabled": false,
"download-dir": "/c/Torrent/",
"encryption": 1,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/c/Torrent/Incomplete/",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": false,
"max-peers-global": 200,
"message-level": 1,
"open-file-limit": 32,
"peer-congestion-algorithm": "",
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-enabled": 0,
"peer-port-random-high": 65535,
"peer-port-random-low": 1024,
"peer-port-random-on-start": false,
"peer-socket-tos": "default",
"pex-enabled": true,
"pidfile": "/var/run/transmission-daemon.pid",
"port-forwarding-enabled": true,
"preallocation": 2,
"prefetch-enabled": 0,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{5dc7a02bbb1d2c7a464b3397689edf6e29b43f8eHLq.c65P",
"rpc-port": 8181,
"rpc-url": "/transmission/",
"rpc-username": "admin",
"rpc-whitelist": "*",
"rpc-whitelist-enabled": true,
"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"speed-limit-down": 100,
"speed-limit-down-enabled": false,
"speed-limit-up": 10,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 0,
"upload-limit": 100,
"upload-limit-enabled": 0,
"upload-slots-per-torrent": 14,
"utp-enabled": false,
"watch-dir": "/c/Torrent/Watch ",
"watch-dir-enabled": true
}
Please help me?
Greetz a frustrated person :-(. - JarnoGGuideI don't know if it matters, but I noticed that in my settings.json, there was no "/" at the end of the directory paths. So
"download-dir": "/c/Torrent/",
would be
"download-dir": "/c/Torrent",
Also, not that you have a space at the end of the path of your watch-dir, is that space also in the name of the directory?
Lastly, I don't know what permissions are set on a new folder if you log in with CIFS using a guest account... - Davidoff007Aspirant@ JarnoG tnx for your comment, i haven't even tried the watch dir because nothing worked at first, but will soon try it out.
It is now possible for me to download torrents, my problem was the incomplete dir, i thought it would be made automatic by transmission but it didn't.
I made it manually and now i'm able to download, maybe this will help the others who are getting the same probs that i have.
Thank you for you patients (or something like that lol).
Edit: The watch dir is also working! :D - ianmacdAspirantGuys, after upgrading to 2.42, the setting to control browser refresh frequency has disappeared.
This was always session-specific anyway and would often revert back to 5 seconds, but at least I could keep changing it. Now, the setting has been removed from Preferences.
Has anyone found a way to get this back? The JS file that one would normally edit to fix this globally is a binary in the ReadyNAS add-on, so I can't make the change there.
Cheers in advance for your help. - endremerkAspirantI'm having the same problem as the guy a bit further up.
Transmission says that "Port is closed" when I check the port in the UI menu.
I've tried a variety of versions, neither of them are working.
I've checked my router, and the port is open. (Even tried to change the port, and I can see that my router automatically changes so that the chosen port is open)
I also tried to use the "in-built" torrent client, but this is not working either.
I recently moved, and as far as I can remember, I was able to use the Transmission Add-On before this.
I've brought the router from my old house, but I've changed the ISP.
I first thought that the ISP in some way was blocking Torrent traffic, until i booted up my Ubuntu machine and tested Transmission from this. Works like a charm.
I'm lost here. Are there any others who have encountered this (and found a solution)?
EDIT:
Oh, and...
Current version:
RAIDiator 4.1.7
Transmission 2.31 - baygaconAspirant2.33 is working a treat if anyone is still having issues with 2.42
Is it possible to have torrent-specific speed limits? If so, how is it configured? - JarnoGGuideI don't know if it's possible with the standard web interface, but Transmission Remote dotnet can.
Right-click on the torrent -> Bandwidth allocation -> download/upload speed
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!