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

Userspace not supported for wireguard implementation in v0.11.0-rc.1 #2535

Open
sachua opened this issue May 26, 2024 · 0 comments · Fixed by #2538
Open

Userspace not supported for wireguard implementation in v0.11.0-rc.1 #2535

sachua opened this issue May 26, 2024 · 0 comments · Fixed by #2538
Assignees
Labels
kind/feature New feature or request

Comments

@sachua
Copy link

sachua commented May 26, 2024

What happened:

When trying to do liqoctl network connect, I faced issues in the wireguard container in gw pod

E0524 09:38:02.429790       1 main.go:81] unable to init wireguard link: cannot create Wireguard interface: cannot add Wireguard interface: operation not supported

It seems that my kernel does not support wireguard yet, userspace implementation was supported in the previous versions, would it be possible to add back support for userspace implementation in the new network implementation?

Environment:

  • Liqo version: v0.11.0-rc.1
  • Liqoctl version: v0.11.0-rc.1
  • Kubernetes version (use kubectl version): 1.24
  • Cloud provider or hardware configuration:
  • Node image:
  • Network plugin and version:
  • Install tools:
  • Others:
@sachua sachua added the kind/bug Something isn't working label May 26, 2024
@cheina97 cheina97 added kind/feature New feature or request and removed kind/bug Something isn't working labels May 26, 2024
@cheina97 cheina97 self-assigned this May 27, 2024
@cheina97 cheina97 linked a pull request May 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants