Replies: 1 comment
-
On startup the browser nodes will perform a DHT query for it's own peer id to find peers close in the KAD-space starting with the bootstrapper. If there are only a handful of nodes that the bootstrapper knows about, it's likely this query will be very short and may even only contain the bootstrapper itself. Once the query is complete the node knows where to start future queries so won't keep discovering peers. It repeats this query periodically. How many peers do you have connected to the bootstrapper? Are you using your node for anything after startup or expecting it to keep discovering peers indefinitely? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I checked some libp2p documents and want to implement an example where a node on the browser side discovers nodes in other browsers. The browser node discovers other browser nodes through a node.js bootstrap node. I used 'kad-dht', but it seems that the browser can only receive the 'peer:discovery' event of the bootstrap node. What I want to ask is: Is my configuration incorrect, or do I need another method to achieve this? The following is my configuration code:
server config:
node config:
Beta Was this translation helpful? Give feedback.
All reactions