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.
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.
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.
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.
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.
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.
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.
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.
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.