-
Notifications
You must be signed in to change notification settings - Fork 822
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
Wireguard between two WSL2 instances and mirrored network mode does not work #10841
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
A workaround has been found for this issue, but it comes at a great cost.
90c90
< if ! cmd ip link add "$INTERFACE" type wireguard; then
---
> # if ! cmd ip link add "$INTERFACE" type wireguard; then
92c92
< [[ -e /sys/module/wireguard ]] || ! command -v "${WG_QUICK_USERSPACE_IMPLEMENTATION:-wireguard-go}" >/dev/null && exit $ret
---
> # [[ -e /sys/module/wireguard ]] || ! command -v "${WG_QUICK_USERSPACE_IMPLEMENTATION:-wireguard-go}" >/dev/null && exit $ret
95c95
< fi
---
> # fi This effectively disables the kernel level Wireguard, forcing to use userspace implementations I realized there might be something missing with mirrored network mode, especially regarding kernel level support. This will be a new feature request for this. |
Windows Version
Microsoft Windows [Version 10.0.22621.2428]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
6.1.21.2-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Expected Behavior
Wireguard should work out of the box.
Actual Behavior
I have two machines on 172.30.0.2 and 172.30.0.6, here is their respective log:
172.30.0.2:
On the other side, 172.30.0.6:
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: