* fix: allow connection between seeds when pex is enabled * chore: add comment to explain `tr_peerMsgs::on_torrent_got_metainfo()` * refactor: remove `tr_swarm::mark_peer_as_seed()` * fix: update seed flag in response to BT msgs Regression from81a42c6bb6* chore: remove redundant code to update peer seed flag * refactor: inc failure count if there were no piece data exchanged * fix: save information from ltep handshake * refactor: rename `tr_peerIo::is_seed_` to disambiguate * fix: add instead of set pex flags when adding non-pex and non-resume peers * fix: don't mark peer as connectable on getting ltep port msg By BEP-11's definition, this flag is only set for peers whom we successfully initiated an outgoing connection with. * refactor: set holepunch flag when we get it from ltep handshake * fix: only accept positive `reqq` in ltep handshake * refactor: handle encryption preference in `tr_peer_info` * refactor: prefer own value for utp support * refactor: make `tr_peer_info::from_first_` const * refactor: handle holepunch support in `tr_peer_info` * fix: parse metadata size only if we have a valid extention id for metadata xfer * refactor: remove `tr_peer_info::add_pex_flags()` as it's no longer needed * fix: correctly handle holepunch support when there is no `m` key in ltep handshake * fix: distinguish between upload only and seed Say we just connected to a partial seed, the peer sends an ltep handshake that has the `upload_only` key, then a BT `Bitfield` message: Without this change, the pex seed flag would be set when parsing the ltep handshake, then immediately unset when parsing the `Bitfield` message. We don't want that. * fix: don't update `tr_peer_info::is_seed_` when merging peer info objects * perf: priority in peer candidate score need 2 bits only * fix: prefer to connect to downloading peers Regression fromc867f00153* chore: add TODO for C++20 opportunity * refactor: don't filter out peers without `ADDED_F_CONNECTABLE` revert change froma2849219f7* refactor: move peer state updates out of peermgr code --------- Co-authored-by: Charles Kerr <charles@charleskerr.com>
About
Transmission is a fast, easy, and free BitTorrent client. It comes in several flavors:
- A native macOS GUI application
- GTK+ and Qt GUI applications for Linux, BSD, etc.
- A Qt-based Windows-compatible GUI application
- A headless daemon for servers and routers
- A web UI for remote controlling any of the above
Visit https://transmissionbt.com/ for more information.
Documentation
Transmission's documentation is currently out-of-date, but the team has recently begun a new project to update it and is looking for volunteers. If you're interested, please feel free to submit pull requests!
Command line interface notes
Transmission is fully supported in transmission-remote, the preferred cli client.
Three standalone tools to examine, create, and edit .torrent files exist: transmission-show, transmission-create, and transmission-edit, respectively.
Prior to development of transmission-remote, the standalone client transmission-cli was created. Limited to a single torrent at a time, transmission-cli is deprecated and exists primarily to support older hardware dependent upon it. In almost all instances, transmission-remote should be used instead.
Different distributions may choose to package any or all of these tools in one or more separate packages.
Building
Transmission has an Xcode project file (Transmission.xcodeproj) for building in Xcode.
For a more detailed description, and dependencies, visit How to Build Transmission in docs
Building a Transmission release from the command line
$ tar xf transmission-4.0.4.tar.xz
$ cd transmission-4.0.4
# Use -DCMAKE_BUILD_TYPE=RelWithDebInfo to build optimized binary with debug information. (preferred)
# Use -DCMAKE_BUILD_TYPE=Release to build full optimized binary.
$ cmake -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo
$ cd build
$ cmake --build .
$ sudo cmake --install .
Building Transmission from the nightly builds
Download a tarball from https://build.transmissionbt.com/job/trunk-linux/ and follow the steps from the previous section.
If you're new to building programs from source code, this is typically easier than building from Git.
Building Transmission from Git (first time)
$ git clone --recurse-submodules https://github.com/transmission/transmission Transmission
$ cd Transmission
# Use -DCMAKE_BUILD_TYPE=RelWithDebInfo to build optimized binary with debug information. (preferred)
# Use -DCMAKE_BUILD_TYPE=Release to build full optimized binary.
$ cmake -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo
$ cd build
$ cmake --build .
$ sudo cmake --install .
Building Transmission from Git (updating)
$ cd Transmission/build
$ cmake --build . -t clean
$ git submodule foreach --recursive git clean -xfd
$ git pull --rebase --prune
$ git submodule update --init --recursive
$ cmake --build .
$ sudo cmake --install .
Contributing
Code Style
You would want to setup your editor to make use of the .clang-format file located in the root of this repository and the eslint/prettier rules in web/package.json.
If for some reason you are unwilling or unable to do so, there is a shell script which you can use: ./code_style.sh
Translations
Sponsors
| macOS CI builds are running on a M1 Mac Mini provided by MacStadium | |
| Free code signing on Windows provided by SignPath.io, certificate by SignPath Foundation |