wsl_portproxy VS WSLHostPatcher

It got pedantic doing this manually between terminals when I have to reset WSL, so I wrote myself a script to do it: https://github.com/toxyy/wsl_portproxy

I had the same problem actually, you need this https://github.com/CzBiX/WSLHostPatcher and just run it under windows, the you need to tell metro to listen to you pc/laptop’s network address

WSL provides a great environment for web developers working on Windows. However, it's not always easy to access the applications running in WSL from the local network. Whether you're working on a web app, a React-Native application, REST API, or have a database residing in a Docker container, you'll need to access it from a real mobile phone or simply from a different device. While there are ways to achieve this, they are not always easy to implement. Some of them require tackling with an NIC Bridge mode or manually downloading and applying a WSLHostPatcher. Which are things you probably don't want to deal with when you're just trying to get your work done. Here's where Expose-WSL comes into play.

So, then your options are: 1) a real HTTP (reverse) proxy like Apache or nginx on Windows, 2) changing your VM network to bridge mode and manually configuring an address every time you start WSL2 (https://stackoverflow.com/a/62438375 , see "option 2"), or maybe 3) https://github.com/CzBiX/WSLHostPatcher this thing

Try this app: https://github.com/CzBiX/WSLHostPatcher. I've checked the code and it isn't harmful at all, it just checks for any wslhost.exe's created connections after the .EXE is run (by just using hooks) and makes it so they listen on all interfaces instead of just localhost, so this effectively makes your WSL2 and Windows listening connections to be merged together in the same network stack, to say it that way. Or in other words, dynamic port forwarding.

This looks good https://github.com/CzBiX/WSLHostPatcher but that’s for tomorrow!