-
Notifications
You must be signed in to change notification settings - Fork 853
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
No internet access before #6939
Comments
Thanks for reporting this @luis-arch . Can you please follow the 'networking-issues' section and share the script output and |
the networking.bat output: wsl.etl is compressed into wsl.zip |
Looking at the logs, this is known issue that should be fixed in insider builds that would trigger if the swap vhd is either compressed or encrypted. This should be fixed by either of
|
thanks,It solve my problem |
Windows Build Number
Microsoft Windows [version 10.0.19042.985]
WSL Version
Kernel Version
5.4.32
Distro Version
kali-linux,aipine
Other Software
Docker Desktop (Windows),version 3.2.2
Visual Studio Code 1.54.3 with Remote-wsl Extension 0.546
v2rayN,version4.17
Repro Steps
after use v2ray's global proxy,my wsl2 network doesn't work.
i want to install alpine-pkg-glibc in my wsl2 alpine.
so i did
then i got
Expected Behavior
I think this is a problem that occurred in alplin alone, but I also had a similar problem in kali-linux afterwards.
Actual Behavior
I found that I can ping the ip of the virtual machine, but ping the external host or even the local computer will show "ping: sendto: Network unreachable"
i use "# ifconfig", and it display nothing
i use "#ifconfig eth0", and it just show
I found that eth0 is missing inet and inet6, which may be the cause of the problem
windows cmd ipconfig show
I use stackoverflow
cann't solve my problem.
i also check #4342, #4275,
#5286
I try to reconstruct the routing table like #5286 ,so i use
when i try the second code,it show
by the time ,
ip addr show eth0
andip route
showFinally, I tried to uninstall docker, wsl, hyper-v, and even the hyper-v virtual network card, reinstall it
but the results are still the same.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: