A few questions about the DHT (BEP 44) protocol

[ac169]

libtorrent project is a rare implementation of DHT (BEP 44) Protocol library, I use c language to achieve DHT (BEP 44) Protocol encountered some problems, the official document is relatively simple, there are a few questions to consult

1. put message Indicates the flow of sending messages without ping -> find_node -> get_peers as long as the peer ip address and port are known.

2. put message Whether the token parameters in the request parameters are generated by the requestor or obtained through get_peers first. The nodes returned by get_peers may have multiple tokens but only one token, so how to correspond is a bit confusing.

3. Is there any official or other third party to provide test nodes, or other ways to facilitate debugging of this protocol?

[arvidn]

put message Indicates the flow of sending messages without ping -> find_node -> get_peers as long as the peer ip address and port are known.

You still need the write-token. This is critical to prevent spoofing the source IP address of the node writing the message.

The nodes returned by get_peers may have multiple tokens but only one token,

What do you mean by this? There's only one token returned by get_peers, right?

Is there any official or other third party to provide test nodes, or other ways to facilitate debugging of this protocol?

I believe uTorrent implements it as well and that a significant number of nodes in the wild implements it. You should be able to test it against the public network.