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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Move Wireguard to (optional) IPv6 endpoint #5

Open
xyzroller opened this issue May 14, 2022 · 1 comment
Open

[FEATURE] Move Wireguard to (optional) IPv6 endpoint #5

xyzroller opened this issue May 14, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@xyzroller
Copy link
Member

Feature request

Feature

If the host server has a public IPv6 address, then use it optionally as endpoint for the wireguard tunnel from the control node.

Purpose of the feature

This will enable IPv6-only host servers in future and will allow control nodes with IPv6 addresses to connect to the host server via an IPv6 wireguard tunnel.

Additional information

Consider using a project domain as endpoint, to support both IPv4 and IPv6 control nodes without having to specify either one or other IP address as endpoint.
@xyzroller xyzroller added the enhancement New feature or request label May 14, 2022
@xyzroller
Copy link
Member Author

Cross links to primary repository and Codeberg issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xyzroller