WSL and two VPN

[Turgaud88]

Windows Version

Windows 11 Pro 26200.7171

WSL Version

2.6.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

Cisco AnyConnect 4.10.04.071

Repro Steps

Hi
I apologize in advance for my poor English.

So, what's the problem, is there windows 11?:
Windows 11 Pro Release
Version 25H2
Installation date 11/22/2025
OS Build 26200.7171
Interaction Windows Component Interface Package 1000.26100.265.0

WSL is installed on this system:
PS C:\Users\Turgaud > wsl --version
WSL version:
2.6.1.0 Kernel version: 6.6.87.2-1
WSLg Version: 1.0.66
MSRDC Version: 1.2.6353
Direct3D version: 1.611.1-81528511
The DXCore version: 10.0.26100.1-240331-1435 .ge-release
Windows Version: 10.0.26200.7171

Note, I do not know why the wsl version says Windows version.: 10.0.26200.7171, I have Windows 11 Pro

So to the core of the problem, I also have two VPNs connected.:

1. My personal VPN, which is deployed on VDS (debian12), running on PPTP and configured at the router level, that is, it connects via the router interface. If this is important, then the Tenda AC6.
   2 router is a working VPN required to connect to Cisco AnyConnect production servers.

What's the problem, for work I need to connect via ssh to my work servers, but when both vpns are connected, I get an error when connecting:
If the WSL network mode is mirrored:
[wsl2]
networkingMode=Mirrored
dnsTunneling=true

Mistake:
OpenSSH_9.6p1 Ubuntu-3ubuntu13.14, OpenSSL 3.0.13 30 Jan 2024
debug1: Reading configuration data /home/turgaud/.ssh/config
debug1: /home/turgaud/.ssh/config line 12: Applying options for *
debug1: /home/turgaud/.ssh/config line 35: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to .hosting..ru [10...223] port 22.
debug1: connect to address 10..*.223 port 22: No route to host
ssh: connect to host .hosting..ru port 22: No route to host

If the WSL network mode is enabled as NAT, then the error:
OpenSSH_9.6p1 Ubuntu-3ubuntu13.14, OpenSSL 3.0.13 30 Jan 2024
debug1: Reading configuration data /home/turgaud/.ssh/config
debug1: /home/turgaud/.ssh/config line 12: Applying options for *
debug1: /home/turgaud/.ssh/config line 35: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to .hosting..ru [10...223] port 22.
debug1: connect to address 10..*.223 port 22: Connection timed out
ssh: connect to host .hosting..ru port 22: Connection timed out

At the same time, if I disable my personal VPN on the router, then everything starts working fine.

As a test, I launched my second debian 12 operating system, and everything works fine there, with both personal and work VPNs enabled. Logically, the problem is somewhere in the WSL.

Expected Behavior

The expected behavior is to connect to production servers via ssh

Actual Behavior

The actual behavior is the inability to establish an ssh connection when two VPNs are enabled.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[Turgaud88]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'