Version 8 (modified by charles, 11 years ago) (diff)



A Blocklist is third-party list of peer addresses to block. This can be used to block peers whose addresses are believed to belong to spyware or malware manufacturers.

What blocklist does Transmission Use?

There is no standard format for these blocklists, but Transmission supports the two most commonly-used formats. Both of them are text files in which each line contains a range of IPv4 "dotted quad" addresses to block and an optional comment:

  • invalid ip:
  • - , 000 , invalid ip

The Transmission Project does not evaluate or endorse any specific blocklists. If you do not know what blocklist to use, you might read about some third-party blocklists and evaluate them on your own.

If "Enable automatic updates" is enabled, Transmission will refresh your blocklist each week.

When you press the `Update Blocklist' button, Transmission will download a new copy of your blocklist.

Adding Other Blocklists

Transmission stores blocklists in a folder named blocklists in its configuration folder.

In that directory, files ending in ".bin" are blocklists that Transmission has parsed into a binary format suitable for quick lookups. When transmission starts, it scans this directory for files not ending in ".bin" and tries to parse them. So to add another blocklist, all you have to do is put it in this directory and restart Transmission.

Using Blocklists in transmission-daemon

transmission-daemon doesn't have an "update blocklist" button, so its users have two options. They can either copy blocklists from transmission-gtk's directory to transmission-daemon's directory, or they can download a blocklist by hand, uncompress it, and place it in the daemon's blocklists folder. In both cases, the daemon's settings.json file will need to be edited to set "blocklist-enabled" to "true".