M
MassimoBor
I have this situation:
[COLOR=rgba(36, 39, 41, 1)]The Host is Windows 10 Pro ver. 20H2
The Host, the Hyper-V VMs and WSL2 all have Internet access; they all can communicate each other, except wsl2 towards the VMs and vice versa (the red arrows).
The Hyper-V VMs use the "Default Switch" vNet: 172.29.96.1, netmask: 255.255.240.0, conn type Internal
WSL2 uses "WSL" vNet: 172.23.240.1, netmask: 255.255.240.0, conn type: Internal
There is a third vNet, named "nat", I can see using "ipconfig" but that is not listed in Hyper-V virtual switch manager: 172.25.128.1, netmask 255.255.240.0, conn type: ?
Can anyone help me? Thanks[/COLOR]
Continue reading...
[COLOR=rgba(36, 39, 41, 1)]The Host is Windows 10 Pro ver. 20H2
The Host, the Hyper-V VMs and WSL2 all have Internet access; they all can communicate each other, except wsl2 towards the VMs and vice versa (the red arrows).
The Hyper-V VMs use the "Default Switch" vNet: 172.29.96.1, netmask: 255.255.240.0, conn type Internal
WSL2 uses "WSL" vNet: 172.23.240.1, netmask: 255.255.240.0, conn type: Internal
There is a third vNet, named "nat", I can see using "ipconfig" but that is not listed in Hyper-V virtual switch manager: 172.25.128.1, netmask 255.255.240.0, conn type: ?
Can anyone help me? Thanks[/COLOR]
Continue reading...