wsl1 vpn connectivity

[dezza]

I've recently switched back to WSL1 and I don't understand why VPN connectivity isn't working. I've tried both OpenVPN and Wireguard and it can't even reach local LAN even if split-tunneling is enabled and works fine otherwise. I tried to search over the issues and web and couldn't find much info that wasn't for wsl2.

I've tried to manually input VPN DNS-server and also my own locally hosted recursive resolver and also public DNS (8.8.8.8, 1.1.1.1).

/etc/wsl.conf

[network]
generateResolvConf = false

I've also tried changing metric of several routes from windows, but with no luck.

IPv4 Route Table (with VPN)
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.0.0.1         10.0.0.2     25
          0.0.0.0        128.0.0.0        10.64.0.1    10.111.40.111      3
         10.0.0.0    255.255.255.0         On-link          10.0.0.2    281
         10.0.0.2  255.255.255.255         On-link          10.0.0.2    281
       10.0.0.255  255.255.255.255         On-link          10.0.0.2    281
    10.125.45.111  255.255.255.255         On-link     10.125.45.111    257
     92.65.87.234  255.255.255.255         10.0.0.1         10.0.0.2     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
        128.0.0.0        128.0.0.0        10.64.0.1    10.125.45.111      1
       172.20.0.0    255.255.240.0         On-link        172.20.0.1      2
       172.20.0.1  255.255.255.255         On-link        172.20.0.1      2
    172.20.44.255  255.255.255.255         On-link        172.20.0.1    257
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link        172.20.0.1    257
        224.0.0.0        240.0.0.0         On-link          10.0.0.2    281
        224.0.0.0        240.0.0.0         On-link     10.111.40.111    257
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link        172.20.0.1    257
  255.255.255.255  255.255.255.255         On-link          10.0.0.2    281
  255.255.255.255  255.255.255.255         On-link     10.111.40.111    257

===========================================================================
IPv4 Route Table (without VPN)
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.0.0.1         10.0.0.2     25
         10.0.0.0    255.255.255.0         On-link          10.0.0.2    281
         10.0.0.2  255.255.255.255         On-link          10.0.0.2    281
       10.0.0.255  255.255.255.255         On-link          10.0.0.2    281
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
       172.20.0.0    255.255.240.0         10.0.0.1       172.20.0.1      2
       172.20.0.1  255.255.255.255         10.0.0.1       172.20.0.1      2
    172.20.44.255  255.255.255.255         10.0.0.1       172.20.0.1      3
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link        172.20.0.1    257
        224.0.0.0        240.0.0.0         On-link          10.0.0.2    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link        172.20.0.1    257
  255.255.255.255  255.255.255.255         On-link          10.0.0.2    281
===========================================================================

Is it because WSL binds to the host interface and not the VPN interface? It seems to have correctly applied default to the VPN interface in WSL:

50: eth3: <BROADCAST,MULTICAST,UP> mtu 65535 group default qlen 1

[eqn-group]

WSL1 is not supported, kindly switch to WSL2

[dezza]

WSL1 is not supported, kindly switch to WSL2

My understanding was that Microsoft reassured everyone that WSL1 was not going to be abandoned?