-
-
Notifications
You must be signed in to change notification settings - Fork 341
Improvement: Send keep alive to peers #44
Comments
I thought about it, but the problem is, when we maintain a fake / deceitful identity in the network for a prolonged period, I am afraid that we might hurt the network. Right now, as you remarked, we do not respond to the An expert's opinion on this would be great actually. I'll ask Arvid Norberg's (the developer of libtorrent) opinion on the matter. |
Mana responds to |
Any news on this topic? |
@mweinelt Arvid Norberg didn't reply (and I don't think he is ever going to reply) but I still think sending keep-alives to peers might harm the network (as I explained above). What do you think? |
We'd probably stay as good peers in their routing tables about forever without adding any value to them. Not sure how fast we have exhausted a peers value, but I guess fast. I don't have a full overview of all the mechanics at play, so my opinion may be of little value. |
Exactly, and that's the problem. =) I'm closing the issue as it'll not be implemented, but feel free to discuss further if you (or anybody) think(s) otherwise. |
Now you are processing only some kinds of responses:
https://github.com/ngosang/magnetico/blob/89a226973bed86237c00648bcaee03cfebadd2ec/magneticod/magneticod/dht.py#L85
if you add:
you will see a ton of "find_node" and "ping" responses.
I'm not sure but I think we should respond (at least to ping) to avoid that the peer think we are offline and stop sending us "get_peers" and "announce_peer" messages.
The text was updated successfully, but these errors were encountered: