-
Notifications
You must be signed in to change notification settings - Fork 855
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wsl2 network didn't work if host ethernet working with vlan #6001
Comments
Yes this! This has taken three hours of my life! I’m assuming what is happening here is that WSL2 network adapter is being bonded to my untagged interface which has no gateway meaning my packets go nowhere. Is this fixable by setting a vlan ID in the guest OS? |
Hello, any update ? |
Please collect WSL logs and post the backlink to the feedback item here. Also please identify any third-party networking software that has been installed on Windows if applicable. |
I've got the same issue. One additional bit of context I can add is that I can connect just fine from Docker containers running in docker desktop. Those should be backed by WSL2 so I'm really confused about what could be different between that and my WSL Ubuntu. Here's the output of network.bat I'm not sure how to include |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Environment
Steps to reproduce
WSL logs:
Expected behavior
if host network works, wsl2 network should work out of box
Actual behavior
if my host network working at vlan mode (host ethernet has vlan id configured), host network everything works(no matter ping/tcp/udp), but wsl2 can not reach any network except host peer (host <-> wsl2 can communicate with each other, but wsl2 can not reach upstream router, or anyother node out of host),
then I reconfigure my host network to non-vlan mode (host ethernet has no vlan id), host network everything works, and wsl2 network also worked.
The text was updated successfully, but these errors were encountered: