NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Transmission mistake in start.sh and settings.json question
Hi all, Not sure if I made this mistake and now it's propegating or it is actually a mistake in the Transmission source for Readynas (which I don't where to look for it). In the start.sh file...
Have tracked it down and here is the issue:
The config file re-writes itself if there is an entry in a format it doesn't like, even though the command line may accept the format.
Some entires in the config files accept wildcards (*), some accept comma deliniated entries such as the rpc whitelist address, some do not. So an IP on the whitelist to allow 192.168.*.* works fine, entering it in the same format for another entry may or may not work. The documentation is sparse on this but it can be found pouring through source.
Furthermore, the command line daemon entires accept for example: 10.0.0.0/8 and actually function with such entires for certain parameters but the config file does not.
Best bet if you want to get fancy, start the entire thing from command line with the exact arguements you want and to heck with the config file OR figure out the exact syntax accepted by the config file. The random ports and others can actually be more than one entry via command line but cannot via the config file. The config file WILL rewrite itself over a bad entry (kinda cool, kinda not) so it keeps n00bs like me from doing dumb things and the process just failing to start and throwing an error in the front-end interface.
Problem solved.
Hi rootuser,
Thank you for sharing to the community.
Let's hear from other members if they have encountered the same problem and seek assistance from super_poussin.
Welcome to the community!
Kind regards,
BrianL
NETGEAR Community Team
Thanks!
There is another settings.json kept under the user profile you started the daemon under (for example) ~/.config/transmission-daemon/settings.json but changing this file has the same problem! Doh!
Apparently this is a well known problem with Transmission. The devs seemed to think it was a good idea to re-write the settings.json file in /data/Transmission/config and those changes are not picked up in any version of Transmission regarless of the port (OSX, *Nix, whatever). The problem is none of the documentation shows where to make the setting changes so it actually works.
In particular there are settings for the port ranges. This is of the utmost importance to me and I want to control the upper and lower port range which is impossible to do in the GUI at this point.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
