So WSL1 was actually using the Windows Kernel so Networking was more straightforward because you had direct access to network syscalls.
WSL2 is a VM in HyperV with some special sauce I guess. Downside is that means you have the same Network setup like you would a VPN.
So when I’m developing a site and use say trunk serve. I can access it locally on my Windows browser even though it’s running on my debian WSL2. However one thing I liked to do on my local network was pull up my smartphone and open ports to look at the mobile view on an actual mobile browser.
Well now open ports in Windows Advfirewall for a service that’s running a Linux VM?
Now do this everytime your WSL2 VM changes it’s local IP (not your LAN IP), and everytime you switch to a service with a different port.
Super PITA and I also broke just the regular local proxy between Windows-WSL2 trying to get it working. So now I just sigh and use the developer tools in Chrome to pretend I’m on a smartphone.
So WSL1 was actually using the Windows Kernel so Networking was more straightforward because you had direct access to network syscalls.
WSL2 is a VM in HyperV with some special sauce I guess. Downside is that means you have the same Network setup like you would a VPN.
So when I’m developing a site and use say trunk serve. I can access it locally on my Windows browser even though it’s running on my debian WSL2. However one thing I liked to do on my local network was pull up my smartphone and open ports to look at the mobile view on an actual mobile browser.
Well now open ports in Windows Advfirewall for a service that’s running a Linux VM?
Now do this everytime your WSL2 VM changes it’s local IP (not your LAN IP), and everytime you switch to a service with a different port.
Super PITA and I also broke just the regular local proxy between Windows-WSL2 trying to get it working. So now I just sigh and use the developer tools in Chrome to pretend I’m on a smartphone.