Seqno request forwarding only considers the same path #169
Assignees
Labels
type_bug
Something isn't working
Comments
LeeSmet
added a commit
that referenced
this issue
May 27, 2024
Previously we just tried to find the same route when forwarding a seqno request. Now we record the forward info in the cache, while also improving the search. That is, we try to forward to a peer we haven't used yet (but we don't do a fanout/broadcast search), and also actually do our very best to forward the request. If we know that didn't work, use a different peer. Fixes #169 Signed-off-by: Lee Smet <lee.smet@hotmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently seqno requests are forwarded naively to "the best route" according to the router. However, in case the request is repeated within some time, it needs to be forwarded to a different route. Currently seqno's aren't used as much, but as the network grows and more unstable links appear, this will be needed to more efficiently resolve connection stalls (compared to just waiting for an expiration on the source entry).
The text was updated successfully, but these errors were encountered: