NatNetwork NatGatewayIpAddress do not work - Element not found about wsl HOT 3 OPEN

I'm pretty sure is intentional. I'm pretty sure we haven't documented this, because we don't want people to rely on it. We've had a lot of discussion about this internally. Would you rather have wsl not launch?

from wsl.

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Lxss /t REG_SZ /v NatGatewayIpAddress /d 192.168.235.1 /f
reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Lxss /t REG_SZ /v NatNetwork /d 192.168.235.0/20 /f

192.168.235.0/20 is not correct CIDR notation for a subnet. You set the number of mask bits to 20, but then set bits after the prefix to non-zero values.
What you probably meant is 192.168.235.0/24, which is the subnet containing the IP addresses 192.168.235.0 - 192.168.235.255.
(If you wanted to create a subnet of size /20 that includes 192.168.235.1, it would be 192.168.224.0/20, which contains the IP addresses 192.168.224.0 - 192.168.239.255. You can use a calculator like this to check your CIDR notation.)

This might be the reason why WSL failed to create the virtual network.

from wsl.

@ReneZeidler Thank you so much! I can't believe I overlooked such a simple mistake for so long.

This feature works beautifully with WSL 2 in NAT mode (the default) to make sure the subnet being used doesn't conflict with something else in the environments you connect to. On or off VPN (Cisco AnyConnect / Secure Client here) it routes the packets and DNS as you'd expect. Thank you for making this feature available WSL team!

If this stays open, I guess the feature request would be to have it warn if an invalid NAT/gateway combo are configured.

from wsl.