wsl2 kali networkingMode=mirrored not functioning right

[ymuuuu]

Windows Version

Microsoft Windows [Version 10.0.26100.2314]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Debian 2024.3 ( Kali-Linux)

Other Software

No response

Repro Steps

sorry if this is too long but first time posting an issue

so i have wsl2 running Kali Linux with network mode made into mirrored thru .wslconfig file, it has been working great
now when i come to solve on HTB CTF machines, i connect to platform using OpenVPN from my host machine (Windows 11)
now when i try to ping the challenge ( to check for connectivity ) I want to solve on HTB using Windows host it works fine and i receive a response back
when i try to do the same on my kali wsl2 there is no response back, although it was working fine before
when i check ifconfig, the IP VPN TUN (eth) is there which means it got attached successfully

└─$ ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.10.16.3 netmask 255.255.254.0 broadcast 10.10.17.255

from windows
` ping 10.10.11.25

Pinging 10.10.11.25 with 32 bytes of data:
Reply from 10.10.11.25: bytes=32 time=186ms TTL=63
Reply from 10.10.11.25: bytes=32 time=68ms TTL=63
Reply from 10.10.11.25: bytes=32 time=66ms TTL=63
Reply from 10.10.11.25: bytes=32 time=67ms TTL=63

Ping statistics for 10.10.11.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 186ms, Average = 96ms`

from WSL
└─$ ping 10.10.11.25 PING 10.10.11.25 (10.10.11.25) 56(84) bytes of data. //stuck

What I tried to debug:
I tired another platform (THM) which uses same way of reaching the machines through OpenVPN and same issue still present
I tried to disable and re-enable WSL from Windows Features
enabled port forwarding
add rule for firewall
disable firewall completely ( bad idea )

I have checked multiple issues before posting here, all point towards the same direction but no final solution

so here is a conclusion for the issue :

• When I connect to the vpn from the OpenVPN client in Windows, I can ping the machines just fine, but when starting a listener inside WSL it seems to not be reachable from the VPN's Network.

• I then tried to connect to the VPN using the OpenVPN client within WSL, which fixes the issue, but (of course) prevents me from accessing a box's http server from outside WSL (Windows Host).

Expected Behavior

to be able to ping the machines from WSL and receive a response back and be able to access the challenge

Actual Behavior

ICMP response is stuck and hold, no response back

Diagnostic Logs

WslLogs-2024-11-26_13-07-48.zip
WslNetworkingLogs-2024-11-26_13-04-01.zip

[github-actions]

View similar issues

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!

Open similar issues:

• Cannot connect Hyper-V VMs(Default Switch) from wsl2 (#11494), similarity score: 0.76
• WSL2 mirrored networking unexpectedly killing connections (#11308), similarity score: 0.75
• Syn-Ack packets intermittently not received inside wsl distro (#12186), similarity score: 0.75

Closed similar issues:

• wsl2 - Network is unreachable with networkingMode=mirrored (#11552), similarity score: 0.79
• Unable to access VPN from WSL2 when networking mode set to mirrored (#11072), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information

Multiple log files found, using: https://github.com/user-attachments/files/17918347/WslLogs-2024-11-26_13-07-48.zip
.wslconfig found
Detected appx version: 2.3.26.0

[CatalinFetoiu]

thanks for reporting the issue. unfortunately, OpenVPN is known to be incompatible with mirrored mode at the moment. This is tracked in #10879

[CatalinFetoiu]

resolving this is a duplicate, we are currently using the other issue to track this problem

/dupe #10879

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!