Running Windows 10 Pro (22H2), WSL 2 1.1.3.0 (according to "Installed version" on Microsoft Store), created the Hyper-V bridged adapter, created the .wslconfig file per instructions, re-launched WSL, but I'm not getting an IP address that can be seen on my network via DHCP, still just seeing the existing, internal IP address. Does this not work with Windows 10 Pro?
Hi Alistair, very helpful. Works great. Question, once using bridging, what needs to be done to connect from WSL2 to Windows? For example, I can connect from Windows to WSL2, such as ssh'ing & ping, but not WSL2 to Windows. Both appear to be on same subnet (10.0.0.*) & turning off Windows Defender didn't help. Does a net route need to be added or something? Any tips would be greatly appreciated. Thank you.
Will this work on Windows 10?
Running Windows 10 Pro (22H2), WSL 2 1.1.3.0 (according to "Installed version" on Microsoft Store), created the Hyper-V bridged adapter, created the .wslconfig file per instructions, re-launched WSL, but I'm not getting an IP address that can be seen on my network via DHCP, still just seeing the existing, internal IP address. Does this not work with Windows 10 Pro?
Hi Alistair, very helpful. Works great. Question, once using bridging, what needs to be done to connect from WSL2 to Windows? For example, I can connect from Windows to WSL2, such as ssh'ing & ping, but not WSL2 to Windows. Both appear to be on same subnet (10.0.0.*) & turning off Windows Defender didn't help. Does a net route need to be added or something? Any tips would be greatly appreciated. Thank you.
Great write-up. Thanks, especially for pointing out the downsides of bridged networking. This helped steer me in the right direction.
Terrible manual. Where to find wired.network ? What to do with genie ? To many questions
Is this still working for you? I've been trying it, but I can't get it to work at all.