wsl-vpnkit VS WSL2-Linux-Kernel

Mirrored network mode sounds quite a lot like what wsl-vpnkit does: https://github.com/sakai135/wsl-vpnkit

This came from Docker Desktop for Windows, where they needed a solution for VPNs like GlobalProtect and AnyConnect that are often configured to drop packets for networks that aren't the main one associated with the VPN.

I'm going to wait a while to see how the new VPN stuff works out. Previously WSL2 didn't work with a Windows VPN without an extra tool ( https://github.com/sakai135/wsl-vpnkit ), hopefully this might fix things, but not going to risk trying it in case it breaks everything.

https://github.com/sakai135/wsl-vpnkit fixes that problem for me, and is less annoying than other fixes I tried

So i installed warp on windows and try to run go mod init to access few packages from my org private repo, and it says the repo not found, So i search and found that WSL 2 need this for Zero Trust to run on WSL 2 : https://github.com/sakai135/wsl-vpnkit , I've download and started the service but it still can't access the repo, does anyone has this problem when developing go with zero trust ?

There's also a reference to https://github.com/sakai135/wsl-vpnkit, which looks like a much more ambitious effort to deal with this.

If it works at all like WSL, you might want to look at wsl-vpnkit.

https://github.com/sakai135/wsl-vpnkit

It's not a proxy, but would give some idea how to shim into the middle.

there's a fix for that! https://github.com/sakai135/wsl-vpnkit

Have you tried wsl-vpnkit?

By the way, Microsoft publishes the WSL kernel source, under GPL, as they must: https://github.com/microsoft/WSL2-Linux-Kernel

From here on out it gets a bit hazy. For kernel builds you will have to use the Microsoft Linux Kernel (don't laugh, it's actually a thing). The USBIPD project walks through a WSL kernel build, so you can use that as a guide of sorts. Once you've done everything you need with the disk, the Gentoo project shows how to import it, but if you already have the VHDX file, I think the import-in-place option may be simpler. Take care in CH2 when making the filesystem. I'm not sure if WSL want's only one ext4 partition or if it walks the disk looking for root. There may be some .wslconfig settings for this, my first guess would be kernelCommandLine.

This was true for WSL1, but WSL2 does contain a Linux kernel. The source code for it is available at:

https://github.com/microsoft/WSL2-Linux-Kernel

git clone --branch mytag0.1 --depth 1 https://github.com/microsoft/WSL2-Linux-Kernel use tag for your version

But if you need a custom kernel then build it by taking Microsoft's kernel config as your base and then set the following up accordingly in your %USERPROFILE%\.wslconfig file:

It uses a customized version of the Linux kernel (repo) that integrates with the host Windows OS. You can build any distro on top of that kernel, as people have done with (of course) Arch. The distro isn't any less "real" than a distro that it run on QEMU (and with a level 1 hypervisor, all systems that uses one are technically virtualized already).

I recompiled the kernel using sources from https://github.com/microsoft/WSL2-Linux-Kernel with experimental genpatches applied.

KERNVER=$(uname -r | cut -f 1 -d'-') git clone --branch linux-msft-$KERNVER --depth 1 https://github.com/microsoft/WSL2-Linux-Kernel.git ~/kern-$KERNVER zcat /proc/config.gz > ~/kern-$KERNVER/.config make -C ~/kern-$KERNVER -j 4 make -C ~/kern-$KERNVER -j 4 modules_install ln -s /lib/modules/$KERNVER-microsoft-standard-WSL2+ /lib/modules/$KERNVER-microsoft-standard-WSL2