For WSL, is the Windows host supposed to have a vlan with the RD WSL image? In Windows, I see my

vEthernet (WSL (Hyper-V firewall))

has an IP in the

172.19.*

range, but in

rdctl shell

, I see the WSL host container IP is

192.168.127.2

, so Windows can't reach ports on this host. Is

wslrelay.exe

supposed to be proxying ports over to Windows with more recent versions (I guess 16+)? I'm sure I've brought this up before, but the Slack workspace has lost the history of past conversations

We set up a network namespace within our WSL distro (because WSL shares the network across all distributions, so stopping and immediately restarting Rancher Desktop sometimes causes network errors when things aren't torn down properly. The namespace ensures the teardown is complete).

wsl-proxy

is used to expose listening ports to the default WSL network namespace. There's also

host-switch.exe

that does the same on the Windows (host) side.