Open h888866j opened 4 months ago
@h888866j Try to run WSLAttachSwitch like this, without using cmd: /mnt/c/Users/August/Download/WSLAttachSwitch.exe "sw2"
I'm running into the same issue. I've tried many different ways running the WSLAttachSwitch.exe program.
I've tried in WSL2, CMD, PowerShell. I've used both /mnt/c and cmd.exe /c methods. They seem to go through, but when I enter 'ip link'
eth1 does not show. (I created a virtual switch in hyper manager before hand)
I think I solved it. Don't use the hypermanager GUI to create the virtual switch. use PowerShell.
run this command in PS to make it:
New-VMSwitch -Name sw2 -NetAdapterName ethernet
Then in the same PowerShell window, cd to where WSLAttachSwitch.exe is saved and run:
.\WSLAttachSwitch.exe "sw2"
After doing this I see eth1 in wsl2 after running: $ ip link
Cheers!
I have sw2 virtual switch,but after runing WSLAttachSwitch.exe "sw2", it does not change anything inside wsl2