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

[spike] WireGuard VPN protocol research #423

Open
xbend opened this issue May 16, 2022 · 2 comments
Open

[spike] WireGuard VPN protocol research #423

xbend opened this issue May 16, 2022 · 2 comments
Assignees

Comments

@xbend
Copy link

xbend commented May 16, 2022

Please analyze the documentation for WireGuard protocol and see what are the different ways a wireguard connection could be established.

We were introduced to peer to peer config, but that requires that each peer knows each-other public IPs. This will be difficult to overcome in Gateway usecase, as Gateways are behind NAT.

Please experiment with a local setup.

@xbend xbend changed the title [spike] Analyze WireGuard VPN protocol [spike] WireGuard VPN protocol research May 16, 2022
@xbend
Copy link
Author

xbend commented May 16, 2022

It is hard to estimate this task. We are setting 8 for a start, but it could take less/more.

@jkmar
Copy link
Contributor

jkmar commented Jun 1, 2022

Summary of the findings so far:

  • Only one of the peers need to know the others endpoint establish connection
  • PeersistentKeepalive option can be used to negate address change effects

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

2 participants