-
Notifications
You must be signed in to change notification settings - Fork 859
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
cannot find device bond0 after recent windows update #9989
Comments
Could this be some change in the kernel? |
I am thinking this got changed? https://github.com/microsoft/WSL2-Linux-Kernel/blob/a733b4e7e4db00d1647ee23022fbcfce33835c61/Microsoft/config-wsl#L1627 How do I bring it back to true or check the param value? |
Thanks for reporting @romarowski. We indeed removed that interface since it didn't seem to be useful to anyone. How exactly were you using this interface ? Is there a reason why eth0 doesn't work ? |
Hello, thanks for your answer. My understanding is that doing it with ether0 could bring connection issues? Very far from having a clue on what I am doing here so not sure. I was able to bring bond0 back up by adding to /etc/networks/interfaces and then Maybe this would have been easier #5352 (comment) |
Ok I see. In this case the easiest would probably to create that interface manually via something like:
See this post with more details You can add this to |
Windows Version
Microsoft Windows [Version 10.0.19045.2728]
WSL Version
1.2.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 20.04
Other Software
I am using bond0 to activate matlab licence inside WSL. This worked until today, I either attribute it to recent Windows update or that I installed an Ubuntu GUI app (Terminator) and all the config that came within.
Repro Steps
ifconfig -a
Used to show a bunch of networks including bond0, I honestly dont remember them.
Expected Behavior
Used to show a bunch of networks including bond0, I honestly dont remember them.
Actual Behavior
Only
eth0:
lo:
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: