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

wgpeerselector takes too much time to recognize broken connections? #69

Open
CodeFetch opened this issue Jan 6, 2022 · 1 comment
Open

Comments

@CodeFetch
Copy link

According to the code it looks like wgpeerselector checks on the connection status every 5 seconds. A connection is seen as broken if there was no handshake in the last 150 seconds. Strangely it appears to take much longer (5-10 minutes) until nodes reconnect. This should be investigated.

@CodeFetch
Copy link
Author

@lemoer As we also need some kind of "automatic balancer" for distributing the WireGuard nodes among the supernodes, it is crucial to have a way to allow a fast reconnect if one "kicks" nodes. Therefore it would nice to add a check on when the received bytes changed and not only on the handshakes.

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

No branches or pull requests

1 participant