Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimization: Keep Connection to Remove DCUtR peers alive #20

Open
1 task
dennis-tra opened this issue Jun 22, 2022 · 2 comments
Open
1 task

Optimization: Keep Connection to Remove DCUtR peers alive #20

dennis-tra opened this issue Jun 22, 2022 · 2 comments
Assignees

Comments

@dennis-tra
Copy link
Collaborator

  • track identify messages and look for changes in advertised relay addresses
@elenaf9
Copy link
Collaborator

elenaf9 commented Jun 25, 2022

I assume you mean "remote" DCUtR peers? Just to help my understanding, could you briefly explain why this is needed?

@mxinden
Copy link
Member

mxinden commented Jun 26, 2022

The optimization is meant for the honey pot, not for the hole punching clients.

Keeping the connections to the (potentially behind a firewall) remote peer alive, as the honey pot, also keeps the identify protocol stream to the remote alive. Keeping the identify protocol stream alive implies receiving identify updates, in particular new relayed addresses, from the remote peer.

Does that make sense? Happy to expand on the reasoning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants