WSL Internal IP Only (Non-Bridged)

[Hyper200]

Hi There,

Thanks very much for the guides, they are really good and i got it working on an external WSL switch.

I had a question though, is there any possability this could work with an internal hyperv switch? I don't really need WSL to be on it own network in the actual network, but with an internal switch it doesn't seem to work

Thanks

Joe.

[luxzg]

Hm, thanks for this question. I did not try, even though I use internal switches regularly. I'll give it a quick test, I don't see why it wouldn't work unless MS explicitly blocked it.

[luxzg]

Seems you're right, this feature works only with external vSwitch. Both Private and Internal refuse to work in my tests past hour or so. I tried existing instances and new ones, tried accessing them from other VMs and host, nothing. It seems as if WSL tells the distro OS that interface is disconnected.

I do wonder if we can fake it ... But, meh, point is not to have workarounds upon workarounds. I'll keep an eye on this feature, see if it surfaces somewhere somehow

[Hyper200]

No worries, Thanks for testing anyway, i was pretty sure this was the case. - Do you think its worth while me reporting this in the WSL Issue too?

Its pretty frustrating that after 3 years we will don't have a way to limit WSL to a vSwitch

[Hyper200]

I ended up raising this as a feature request in WSL - microsoft/WSL#9251

[luxzg]

All I can say is - you get my upvote, and good luck! We waited for... Well, forever, just to get any kind of proper networking. They sure are terribly slow with any of networking requests or bugs. Hope yours gets worked on faster, since really it should "just work" once they finally enabled bridging and using vSwitch of any kind.