-
Notifications
You must be signed in to change notification settings - Fork 285
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
Closing old connection #430
Labels
1.1
Issue related to Tinc 1.1
bug
Issues in which the users gave a clear indication to the causes of the unexpected behaviour
solution_exists
A solution for the issue has already been suggested in the discussion.
Comments
300-Skip-Autodisconnecting-for-ConnectTo-node.patch
|
Thanks ! |
When two nodes connect to each other at exactly the same time, one node should drop its connection. A deterministic tie breaker should be implemented here. |
gsliepen
added
bug
Issues in which the users gave a clear indication to the causes of the unexpected behaviour
solution_exists
A solution for the issue has already been suggested in the discussion.
1.1
Issue related to Tinc 1.1
labels
Mar 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
1.1
Issue related to Tinc 1.1
bug
Issues in which the users gave a clear indication to the causes of the unexpected behaviour
solution_exists
A solution for the issue has already been suggested in the discussion.
Hello,
I've 2 nodes in tinc version 1.1pre18
Both nodes listening on 65000
Established a second connection with b8_27_eb_23_73_87 (26.0.0.77 port 65000), closing old connection
Why it closes the only connection ? It's the only one working. Then there is a loop for about ~40 sec :
After a while ~ 1 minute. It's working weel.
Any idea why this strange behavior ?
The text was updated successfully, but these errors were encountered: