-
Notifications
You must be signed in to change notification settings - Fork 282
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
SegFault when using TunnelServer=yes #247
Labels
1.0
Issue related to Tinc 1.0
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
potentially_fixed
This might have been fixed, awaiting confirmation.
Comments
Version: 1.1 Some time has passed but I think the problem also exists with only 1.1 nodes. However I've migrated to another VPN solution and cannot assist with tests anymore. Sorry. Best of luck |
gsliepen
added a commit
that referenced
this issue
Jul 20, 2021
We could have a REQ_KEY coming from a node that is not reachable; either because DEL_EDGEs have overtaken the REQ_KEY, or perhaps if TunnelServer is used and some nodes have a different view of reachability. This might fix GitHub issue #247.
This might be fixed by commit ed070d7. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
1.0
Issue related to Tinc 1.0
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
potentially_fixed
This might have been fixed, awaiting confirmation.
I have a network with about ~800. The network is a mix of tinc 1.0 and
1.1 nodes. It is gradually expanding for several years now.
The problem is that at some point it seams the daemon can not handle the
processing of the new connection and the edges.
There are 3 major nodes in the system and every other node initially
makes connection to one of them.
Now after a lot of debugging I've limited to all nodes to connect only
to one node, and use iptables to grant new connections gradually. last
limit was 5 per minute.
I've started to monitor how the edges are growing on the main node and I
see that although I've limited the connections on the other 2 major
nodes at some point there are rapid spikes in the edges when new
connection is established.
So my guess is that the other nodes have a previous state on the edges
when they try to push it, that is causing the main nodes to become
overwhelmed.
So I've decided to put TunnelServer=yes on the major nodes so they don't
propagate the connections on the other nodes.
However I get a segfault soon after starting on each node that I enable
that option.
I've build from the latest code and here is a trace of such a run: (this
is not from a "major" node, but the effect is the same)
Any help is much appreciated since my network is unusable at the moment
The text was updated successfully, but these errors were encountered: