Transmission

Kind of self-explanatory, I hope. I'm not too familiar with transmission-daemon, but I'm wondering how much of the settings/preferences from the GUI Transmission are used in the daemon. In particular, will the IP Block list that I have set up in Transmission work in the daemon?

Ah, thanks. Anyway to test it to make sure I did it right? I'm using a link to a .gz file, does that work?

d00derino wrote:I'm using a link to a .gz file, does that work?

No, the link is no problem, the compression is something the daemon is not expecting. You'll have to decompress the file yourself.

Thanks, I found the page that explains it better, I unzip it and put it into the blocklists folder. I assume there isn't a way to tell if it's working though, is there? Like a log kept?

There's more to make it work, the daemon has to be restarted or (I've never used this with the daemon) made to update (with transmission-remote --blocklist-update) but I think this last option is different...

When the daemon starts it looks into the blocklists directory and tries to convert any file there to its own format (the .bin files); the --blocklist-update uses the URL stored in settings.json to download a new list and then converts it.

- - - - -

About testing, if you built the daemon yourself, you'll find a series of tools in the libtransmission directory. Those tools are just test programs which are not installed, and there is one for testing the block lists.

Hmmm, I did not build it myself, but rather just apt-get'd it.

Where did you find that snippet of Wiki? All I was able to find was something telling me to extract it and where, and not even what files are supported so I used a .txt and a .dat. Is there a Wiki page that tells me the tools it should come packaged with to see if the files in my blocklist folder are being used?

Correction: According to this https://trac.transmissionbt.com/wiki/Blocklists it does support compressed files.

What "snippet of Wiki"? You mean my last comment, its my comment, not a copy from somewhere. Its just like I said, the building process creates a lot of executables that are not installed, they are tests which I guess the developers just leave there (a waste of time for anybody else building from source).

If the daemon created .bin files from your blocklists, then it is using them. No, there are no log messages about each time it blocks an outgoing connection.

x190 wrote:AFAIK, blocklists need to be in text form when adding manually. GUI clients that support auto updates via a URL can handle compressed files.
Somebody needs to clarify this in the wiki and Help files as many users are confused by the current wording.

Yes. This a million times. I have a .txt file and a .dat file in my folder, and haven't been around to check, but the wording is very confusing.

Edit: Also, it seems it hasn't created .bin files, despite having the correct settings in settings.json.