WSL2 Port forwarding port to linux

wsl2-network.ps1

$remoteport = bash.exe -c "ifconfig eth0 | grep 'inet '"
$found = $remoteport -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';

if( $found ){
  $remoteport = $matches[0];
} else{
  echo "The Script Exited, the ip address of WSL 2 cannot be found";
  exit;
}

#[Ports]

#All the ports you want to forward separated by coma
$ports=@(80,443,10000,3000,5000);


#[Static ip]
#You can change the addr to your ip config to listen to a specific address
$addr='0.0.0.0';
$ports_a = $ports -join ",";


#Remove Firewall Exception Rules
iex "Remove-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' ";

#adding Exception Rules for inbound and outbound Rules
iex "New-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' -Direction Outbound -LocalPort $ports_a -Action Allow -Protocol TCP";
iex "New-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' -Direction Inbound -LocalPort $ports_a -Action Allow -Protocol TCP";

for( $i = 0; $i -lt $ports.length; $i++ ){
  $port = $ports[$i];
  iex "netsh interface portproxy delete v4tov4 listenport=$port listenaddress=$addr";
  iex "netsh interface portproxy add v4tov4 listenport=$port listenaddress=$addr connectport=$port connectaddress=$remoteport";
}

@Esensats great work.

This is probably user error, but after executing this script I am no longer able to use my browser on Windows to reach a server running on 127.0.0.1 in WSL. I also cannot reach it through the IP associated with WSL in ipconfig.

Basically I am now further from the original goal as I was. Not only can I not reach the server from another device, I also cannot reach it from the windows machine running WSL itself.

This has also persisted after removing the Firewall rules. At this point I don't even know how to fix this problem. Turning off the firewall entirely has also not fixed this, so there must be a different issue at play than the firewall...

Remote Development in VSCode also has stopped working, likely due to the same issue. Somehow this script (or more likely, Windows itself) has completely broken WSL.

Even after completely reinstall WSL I now cannot reach it in anyway from the host machine, except by opening it in a terminal. I would advise anyone to reconsider using this script. I don't know what exactly about it has caused this, but it has completely bricked my system.

@edwindijas Since then I made a CLI tool called pfwsl inspired by your script. With it you can type pfwsl add 8080 (or multiple: pfwsl add 80,443,22) and it'll add all of the netsh and firewall rules automatically. It's also as easy to disable the forwarding with pfwsl rm or pfwsl rm 443,80.

It has some extra features like finding all firewall rules on specified ports (pfwsl find 8080), listing currently enabled rules (pfwsl ls) etc!