dht-sniffer


Introduction

A nodejs based dht-sniffer, including a metadata(torrent) module that can be used to fetch and parse metadata of torrents.

Example

``js
const { DHTSniffer } = require('../lib/dht-sniffer');
const fs = require("fs");
const path = require("path");

let sniffer = new DHTSniffer({ port: 6881, refreshTime: 30000 });
sniffer.start();

// "infoHash" event will fire when the sniffer get a infoHash
sniffer.on('infoHash', data => {
console.log('get infoHash:', data, data["infoHash"].toString("hex"));
// can be removed, fetch the metadata of the target infoHash
sniffer.fetchMetaData(data['infoHash'], data['peer']);
});

// "metadata" event will fire when the sniffer fetch the target metadata successfully
sniffer.on("metadata", data => {
console.log("success", data["infoHash"], data["metadata"]);
try{
fs.writeFileSync(path.join(__dirname,"../tors/",${data["infoHash"].toString("hex")}.torrent),data["metadata"]);
}catch(e){
fs.writeFileSync(path.join(__dirname,${data["infoHash"].toString("hex")}.torrent),data["metadata"]);
}
})

sniffer.on('warning', err => {
console.error(err);
});
sniffer.on('error', err => {
console.error(err);
});
sniffer.on("metadataError", data => {
console.error("fail", data["infoHash"], data["error"]);
})

`


API

$3

Start sniffing infoHash from the DHT network, should be called after initializing the service.

$3

Stop the sniff service and destroy the inner DHT instance.

$3

Fetch the target metadata from the target peer.
`js
sniffer.fetchMetaData({
infoHash:Buffer,
peer:{
host: any //target ip address,
port: any //target port number
}
})
`

$3

Parse the raw metadata to a object with the following properties:
`js
{
infoHash,// Buffer like infoHash
name, // the name of the metadata
size, // total size of the files
torrentType, // 'single' or 'multiple' files
filePaths, // a list of all files
info: metadata.info,
rawMetadata
}
`

$3

In real world practice, some peers will only send useless infoHashes, whose metadata can not fetched from the original source. These peers may be also dht-sniffers, so this sniffer mark those peers that sent useful infoHashes as useful peers. Export them and reuse next time can help to speed up next execution of the sniffer.

$3

Import a peer. peer:{host,port}

$3

Generally, the waiting queue will store many awaiting infoHash after hours of sniffing. However, if the sniffer is aborted, such in-memory data will be lost. Hence, there is a method called exportWaitingQueue offered to export these data and make the storage of the data available.

$3

Import an array of waiting queue.

Events

$3

Emitted when the "get_peers" message is received, the message consists of an infoHash Buffer data and the remote peer which sent the "get_peers" message, be like { host, port }.

$3

Emitted when the service fetched target metadata successfully. The metadata argument is a buffer that can be saved as a torrent file directly. Besides the metadata argument can also be parsed into an object using the parseMetaData function.

$3

Emitted when the service encounter an error during the metadata fetching progress.

Options

$3

The port number of the DHTSniffer service. Default is 6881.

$3

If the sniffer have not received any message from the DHT network during a time period, if will sent the find_node message to other nodes. By default the refreshTime is set to 1 minute, i.e. 1601000 ms.

$3

Because every metadata request will last for seconds, the service will fetch metadata parallel. This option is used to limit the number of the parallel requests. Default value is 16.

$3

While there is more than 25 (or your setting value) metadata requests, the call of sniffer.fetchMetaData function will be put into a waiting queue. This option is to set the size of the waiting queue. Default value is -1 which means no limit.

$3

If the pending request exceeds this value, it will time out. Default value is 30*1000 ms.

$3

Boolean value. If true, the service will look for other nodes very aggressive. Default value is false.

$3

Boolean value. If true, the service will ignore fetched requests this are still kept in the fetched cache. Default value is true.

$3

The number of concurrent requests of the DHT service, mainly related to the find_node requests. Default value is 16, and it is enough under most circumstances.

$3

The size of the internal LRU cache fetchedTupleSize which will store the tuple like {infoHash, peer}. While the ignoreFetched option is set to true and the tuple is still kept in cache, the metadata fetching requests will be ignored.

$3

The default is set to 0. In general, the sniffer will only try to fetch one torrent with the same infoHash at a time. This can help improve the efficiency of the sniffer by avoiding fetching duplicate torrents. However, if the sniffer only fetches one or two infoHashes, this feature can slow down the process of fetching a single infoHash. So this option can be set to a value of 0~1` to increase the number of parallel fetches of the same infoHash.