deal with sending DHT messages to own node #67

New issue

Closed

opened 2020-08-24 19:21:32 +02:00 by schmittlauch · 1 comment

schmittlauch commented

2020-08-24 19:21:32 +02:00

Owner

Sometimes messages are sent from the node to its own listening server port. There can be several reasons for that:

node mistakenly ends up in own cache (although we try to prevent that)
multiple vservers might need to send messages to each other
need to (re)join but node to join on somehow still has own node as a stale entry

Currently messages sent from a node to its own listening port are not getting responded to.

Sometimes messages are sent from the node to its own listening server port. There can be several reasons for that: - node mistakenly ends up in own cache (although we try to prevent that) - multiple vservers might need to send messages to each other - need to (re)join but node to join on somehow still has own node as a stale entry Currently messages sent from a node to its own listening port are not getting responded to.