skip to Main Content
Client Options

Client Options

bittorrent client client options

Choking Algorithm

Fixed Slots is the traditional choker with a fixed number of unchoke slots.

Rate based opens up unchoke slots based on the upload rate achieved to peers. The more slots that are opened the marginal upload rate required to open up another slot increases.

BitTyrant attempts to optimize download rate by finding the reciprocation rate of each peer individually and prefers peers that gives the highest return on investment. It still allocates all upload capacity, but shuffles it around to the best peers first. For this choker to be efficient, you need to set a global upload rate limit.

Seed Choking Algorithm

Round Robin distributes the upload bandwidth uniformly and fairly. It minimizes the ability for a peer to download everything without redistributing it.

Fastest Upload unchokes the peers we can send to the fastest, this might be a bit more reliable in utilizing all available capacity.

Anti Leech prioritizes peers who have just started or are just about to finish the download. The intention is to force peers in the middle of the download to trade with each other.

Use the Network Address Translation Port Mapping Protocol (NAT PMP)

When checked the listen port and the DHT port are attempted to be forwarded on the router through NAT-PMP.

Use Universal Plug And Play (UPNP)

When checked the listen port and the DHT port are attempted to be forwarded on local UPnP router devices.

Ignore nonrouters

Indicates whether or not the UPNP implementation should ignore any broadcast response from a device whose address is not the configured router for this machine.

Reopen Sockets

If clicked Koinonein BitTorrent Client will reopen the outgoing and listen sockets.

Use the distributed tracker service (DHT)

If checked Koinonein BitTorrent Client will be able to use trackerless torrents.

You can read more about DHT here.

Announce interval

The number of seconds between announcing torrents to the DHT, default is 900 seconds.

Block rate limit

The max number of packets per second a DHT node is allowed to send without getting banned.

Block timeout

The number of seconds a DHT node is banned if it exceeds the rate limit. The rate limit is averaged over 10 seconds to allow for bursts above the limit.

Item lifetime

The number of seconds a immutable/mutable item will be expired. default is 0, means never expires.

Maximum DHT items

Maximum number of items the DHT will store.

Maximum fail count

The maximum number of failed tries to contact a node before it is removed from the routing table. If there are known working nodes that are ready to replace a failing node, it will be replaced immediately, this limit is only used to clear out nodes that don’t have any node that can replace them.

Maximum peers

The max number of peers to store per torrent for the DHT.

Maximum peers to send in reply

The maximum number of peers to send in a reply to get peers.

Maximum torrents in search reply

The max number of torrents to return in a torrent search query to the DHT.

Maximum torrents to track

The total number of torrents to track from the DHT. This is an upper limit to make sure malicious DHT nodes cannot make us allocate an unbounded amount of memory.

Number of concurrent search request

The number of concurrent search request the node will send when announcing and refreshing the routing table. This parameter is called alpha in the Kademlia paper.

Aggressive lookups

Changes the lookup behaviour in terms of how many outstanding requests are kept. Instead of having branch factor be a hard limit, Koinonein BitTorrent Client always keep branch factor outstanding requests to the closest nodes. i.e. every time we get results back with closer nodes, we query them right away. It lowers the lookup times at the cost of more outstanding queries.

Enforce node id

If checked, node’s whose ID’s that are not correctly generated based on its external IP are ignored. When a query arrives from such node, an error message is returned with a message saying “invalid node ID”.

Extend routing table

Makes the first buckets in the DHT routing table fit 128, 64, 32 and 16 nodes respectively, as opposed to the standard size of 8. All other buckets have size 8 still.

Ignore dark internet

Ignore DHT messages from parts of the internet Koinonein BitTorrent Client wouldn’t expect to see any traffic from.

Privacy lookups

If checked, Koinonein BitTorrent Client perform lookups in a way that is slightly more expensive, but which minimizes the amount of information leaked about you.

Read only

I checked, the other nodes won’t keep this node in their routing tables, it’s meant for low-power and/or ephemeral devices that cannot support the DHT, it is also useful for mobile devices which are sensitive to network traffic and battery life. this node no longer responds to ‘query’ messages, and will place a ‘ro’ key (value = 1) in the top-level message dictionary of outgoing query messages.

Restrict routing IP’s

Determines if the routing table entries should restrict entries to one per IP. This defaults to checked, which helps mitigate some attacks on the DHT. It prevents adding multiple nodes with IPs with a very close CIDR distance.

When checked, nodes whose IP address that’s in the same /24 (or /64 for IPv6) range in the same routing table bucket. This is an attempt to mitigate node ID spoofing attacks also restrict any IP to only have a single entry in the whole routing table

Restrict search IP’s

Determines if DHT searches should prevent adding nodes with IPs with very close CIDR distance.

Bootstrap nodes

This is a comma-separated list of IP port-pairs. They will be added to the DHT node as back-up nodes in case Koinonein BitTorrent Client does not know of any. This setting defaults to:,


If clicked all DHT settings are applied.

Use the Local Service Discovery service (LSD)

Provides a SSDP-like, http over udp-multicast, mechanism to announce the presence in specific swarms to local neighbours.

You can read more about LSD here.

Announce interval

The time between local network announces for a torrent. This interval is specified in seconds and defaults to 300 seconds.

Broadcast LSD

If checked, the local peer discovery (or Local Service Discovery) will not only use IP multicast, but also broadcast its messages. This can be useful when running on networks that don’t support multicast. Since broadcast messages might be expensive and disruptive on networks, only every 8th announce uses broadcast.

Network adapter lock

If checked Koinonein BitTorrent Client will only use the currently checked network adapters.

If you uncheck this then that has the same effect as deselecting all adapters then clicking Apply however if you check this no change will happen until you click Apply.

There is no fall back option so if Koinonein BitTorrent Client is started and the network adapter is unavailable Koinonein BitTorrent Client won’t be able to connect until you set a new adapter or reconnect the missing adapter.


When clicked Koinonein BitTorrent Client will connect to all adapters if Network Adapter Lock is unchecked or just connect to the checked adapters if Network Adapter Lock is checked.

Changes take a few seconds to implement as all connections get closed and then the new connections opened.

You can press F9 at any time to get the currently used adapters entered into the log.


Rechecks what adapters are available.

Koinonein BitTorrent Client uses two ports, one standard port and one SSL port.

You can select your own port numbers and they will be used each time Koinonein starts or you can select a random port or have Windows pick the free ports for you.

If you need to change the ports you can do so by setting the port numbers then click Change.

No Proxy

If selected no proxy will be used.

HTTP – Authentication

If selected it will be assumed that a HTTP proxy is being used that requires a user name and password.

HTTP – No Authentication

If selected it will be assumed that a HTTP proxy is being used that does not requires a user name and password.

i2p SAM Proxy

If selected an i2p SAM proxy will be assumed to be used.


If selected it will be assumed that a SOCKS4 proxy is being used that requires a user name.

SOCKS5 – Authentication

If selected it will be assumed that a SOCKS5 proxy is being used and a user name and password will be sent if required.

SOCKS5 – No Authentication

If selected it will be assumed that a SOCKS5 proxy is being used that does not requires a user name and password.

i2p Hostname

The i2p SAM bridge to connect to.

Proxy Hostname

The hostname where the proxy is running.

Proxy Username

The proxy username.

Proxy Password

The proxy password.

Allow mixed i2p connections

If selected i2p torrents can get peers from other sources.

Hostname lookups via proxy

If selected hostname lookups are done via the selected SOCKS5 or HTTP proxy.

Make peer connections over proxy

If selected peer connections are made and accepted over the selected proxy, web seeds are included in this.

Make tracker connections over proxy

If selected tracker connections are made over the selected proxy.

Proxy Port Number

The port number the selected proxy will use.

i2p Port Number

The i2p SAM bridge port number.


When clicked all settings in the Proxy – i2p section are applied.

If you click Reset Koinonein BitTorrent Client will revert to it’s default settings, you won’t lose any torrents.

Close search
Back To Top