{"id":614,"date":"2009-08-07T23:55:41","date_gmt":"2009-08-07T23:55:41","guid":{"rendered":"http:\/\/wiki.davelevy.info\/?p=614"},"modified":"2024-11-10T23:26:44","modified_gmt":"2024-11-10T23:26:44","slug":"bittorrent","status":"publish","type":"post","link":"https:\/\/davelevy.info\/wiki\/bittorrent\/","title":{"rendered":"Bittorrent"},"content":{"rendered":"

I have looked at Bittorrent on and off over the years. It was controversial as it was the preferred filesharing solution of choice for copyright pirates but it has significant other uses and benefits. It was probably designed to  cope with site or server bandwidth scarcity in a client server transaction. I first created this page in May 2009 as a result of and to aid my experimentation with bittorrent clients. I had another look 10 years later and significantly updated the page to document my experiments with deluge on raspbian. In 2023, I had another go. As ever, see below\/overleaf for my notes.<\/p>\n

One of my inspirations was to create a bittorrent swarm for my snipsnap binaries. My experiments involved using the then named “Open Office” which had its own torrent download. (In one solution, I would act as a seeder and in the second I would act a peer. (It seems these words are actually synonymous).<\/p>\n

    \n
  1. The Wikipedia Page<\/a> … always a good place to start<\/li>\n
  2. A review of the economics and history<\/a> of the founding company by Simon Morris; I take from this that bittorrent the company protected itself from closure and legal attack by managing its intent i.e. working hard to avoid illegal use and recognising that there were “substantial non-infringing use-cases”.<\/li>\n
  3. Also What is a seedbox and why would you want one<\/a>?<\/li>\n<\/ol>\n

    2019<\/h3>\n
      \n
    1. BitTorrent Beginner’s Guide: Everything You Need to Know<\/a>, they say, “BitTorrent file-sharing technology isn’t just for pirates. Here’s how to access the rich troves of legitimate and legal content.” They list their top three clients.<\/li>\n
    2. 25 Best Torrent Sites (Most Popular in 2020)<\/a>, an article on the protocol and the role of trackers, listing the most popular at the time of publication.<\/li>\n
    3. Downloading your First Torrent: The Definitive Guide (2020 Update)<\/a>, by Rapidseed, they offer a proxy service but the article summarises the protocol well.<\/li>\n
    4. The Best VPNs for Torrenting 2020 – Should you torrent a VPN?<\/a>, by proprivacy; let’s all remember that both torrenting and privacy & anonymity are legal, and in many ways protected human rights law.<\/li>\n<\/ol>\n

      2023<\/h3>\n
        \n
      1. How to create a torrent using the command-line<\/a>, at AskUbuntu recommends a couple of tools . This all takes me back to opentracker<\/a> , but I misunderstood the role of trackers. (They are not indexers).<\/li>\n
      2. However, this at linuxconfig<\/a>  documents the transmission<\/em> daemon, and the daemon ports. Finally I found Bittorrent: Set<\/a> by Niel Bothwick at linux format. I installed transmission, using these instructions<\/a>, except I used ip-tables<\/code><\/acronym> to set the firewall rules<\/a>, this, for some reason, required a system reboot<\/a>. I used transmission-create<\/code> to make a .torrent file, take notice of the arguments, the output file and the tracker need to be specified; when complete I placed the torrent on my web site, and the transmission web interface, sensibly allows one to specify an http URL for the torrent file. However the invoking  URL is fragile<\/a>, it needs ~\/transmission\/web\/. On logging in to get some stats, using the command line, transmission-remote, I was rejected<\/a> on numerous occasions. transmission-remote’s man page<\/a> is helpful and cli-ck.io have a page<\/a> on transmission-remote, documenting the -a i.e. the add flag. See also Transmission’s home pages<\/a>.  Is that it? Install and start the daemon, make a torrent file, then notify the daemon about the torrent.<\/li>\n
      3. I needed to set a router port forwarding rule<\/span>, which requires the use of the IP number, not the DNS name, and I had to install a new rule<\/a>. (I used, yougetsignal.com<\/a> and canyouseeme.org<\/a> to test that the rule was working. When editing the transmission settings file<\/a>, remember to take a copy, oh for versioning file systems.<\/li>\n<\/ol>\n

        Ubuntu<\/h3>\n

        There is quite a lot of choice<\/a> if using Ubuntu, and it ships with a package called Transmission<\/a>. I also found this article on using transmission<\/a> at superuser.com and this article at morehawes<\/a>  and this at askubuntu<\/a>, and this at linuxconfig<\/a> which documents the transmission<\/em> daemon, the latter documenting ports required and having a copy of the settings file. Also https:\/\/www.cnx-software.com\/2012\/06\/08\/how-to-create-and-seed-a-torrent-in-ubuntu-using-transmission-command-line\/<\/a> which is clearer about how to avoid an indexer.<\/p>\n

        In 2023, I found this, on making a torrent from the command line<\/a>, which confused me on how to publish the torrent. See also ctorrent, a CLI only tool and its user manual<\/a>, and this how to,<\/a> which recommends bittornado<\/code> which seems unavailable for U22.04 and raspbian.<\/p>\n

        Opentracker<\/h3>\n

        They say<\/a>, “opentracker<\/em> is a open and free bittorrent tracker<\/a> project. It aims for minimal resource usage and is intended to run at your wlan router. Currently it is deployed as an open and free tracker instance. Read our free and open tracker blog<\/a> and announce your torrents there (but do not hesitate to setup your own free trackers!).”<\/p>\n

        The -h switch displays the usage string, the –help flag displays more hints. I need to read<\/em> the compiler directing statements more carefully. Especially related to compression<\/a> and  access lists.<\/p>\n

        See,<\/p>\n

          \n
        1. opentracker.conf.sample<\/a> , a sample conf file for opentracker<\/li>\n
        2. How to create torrent files<\/a> from techspree<\/em>, this also talks of the trackers and lists<\/a> some of the tracker’s announcement URLs.<\/li>\n<\/ol>\n

          I have come to the view that I don’t need my own tracker. I found two tracker sites whose names I like, probably both powered by erdgeist i.e opentracker.<\/p>\n

            \n
          1. https:\/\/www.cyberia.is\/tracker.html<\/a><\/li>\n
          2. https:\/\/opentrackr.org\/<\/a><\/li>\n<\/ol>\n
            \"\"<\/a>
            An illustrative bittorrent network, the role of the tracker<\/figcaption><\/figure>\n
              \n
            1. The initiator makes a torrent file , notifies the tracker and publicises the URL of the .torrent file.<\/li>\n
            2. Peers commence Uploads and both notify the tracker and request peer locations from the tracker.<\/li>\n
            3. Each peer holds a copy of the data.<\/li>\n<\/ol>\n

              Raspbian & Deluge<\/h3>\n

              I experimented with Deluge; I never<\/strong> got this work, the slugged functionality on raspbian was a problem and I never found a tracker. I got as far as installing deluge which would allow me to participate in a swarm as a peer, but not as an initiating seed.<\/p>\n

              Deluge seems the PI tool of choice, I found this<\/a> at PiMyLifeUp, and this on youtube<\/a> and How to Turn a Raspberry Pi into an Always on BitTorrent Box<\/a> this is to support the peer role. See also “How to make a torrent file<\/a>” from helpdesk geek. rapidseedbox have a number of resources; here is a user manual, from Rapid Seedbox, on creating a new torrent<\/a>. See aslo how to use deluge<\/a> from wikihow. Using the GTK tool which needs the application password, to remotely connect in my use case.<\/p>\n

              I used google to search for trackers and further resources on running a bit torrent server<\/a> on raspbian. See also the comment dated 14th January<\/a> for more on deluge and raspbian which I have moved to the comments.<\/p>\n

              Early findings<\/h3>\n

              Most of these were found in the early days of this page.<\/p>\n