Updating Routing tables #66
Replies: 1 comment
-
Hello, First of all, I'm glad to see someone dedicated themselves to put the library into a real use. That's where the bootstrap node grabs node informations of closest nodes to a destination. Another thing that comes to my mind the generation of "Node ID". Are you sure they are unique? I don't see any validation logic and perhaps you'd want to add it later, but nodes should have unique ids, otherwise your bootstrap node may not return itself in the response (I guess) and that check is done by checking node ids in its routing table. You could use this code example to print the routing table of the bootstrap node and see whats up. P.S: the logic in |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am trying to connect multiple nodes which run in docker containers , first to the bootstrap node , then they should update their DHTs , the nodes connect to bootstrap and send FIND_NODE_REQ but bootstrap doesn't return FIND_NODE_RES with the information about the nodes that already connected to it ( so it doesn't update it's table ) yet they send PING-PONG... Can you please tell me what I am doing wrong?
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions