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

Got invitation from XXXX but we don't have an invitation key #128

Open
alfreddatakillen opened this issue Oct 24, 2016 · 2 comments
Open
Labels
1.1 Issue related to Tinc 1.1 needs_investigation Unexpected behaviours with uncertain causes - needs more investigation

Comments

@alfreddatakillen
Copy link

Hello!

I keep running into a problem with invitations, using 1.1pre14.

I have a machine designated to create invitations to other machines in my network. First time I start tinc after reboot, tinc will respond to invites with Got invitation from X.X.X.X port XXXXX but we don't have an invitation key. However, after doing a tinc reload, it will start accepting invites. From time to time it starts responding with the same error again, until I do a tinc reload again.

When creating the invites, there is never any errors, and there is a new file created in the invitations directory each time.

The machine's config is:

AutoConnect = yes
AddressFamily = ipv4
DeviceType = tap
LocalDiscovery = yes
Mode = switch
Name = hub
PingInterval = 30
PingTimeout = 5
ProcessPriority = high
@tomberek
Copy link

I have noticed this as well so I just have a script that restarts that instance of tinc whenever I create an invite.

@fangfufu
Copy link
Collaborator

Does this still affect 1.1pre17?

@fangfufu fangfufu added needs_investigation Unexpected behaviours with uncertain causes - needs more investigation 1.1 Issue related to Tinc 1.1 labels Jun 23, 2021
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 needs_investigation Unexpected behaviours with uncertain causes - needs more investigation
Projects
None yet
Development

No branches or pull requests

3 participants