Open AllanChain opened 3 years ago
View Post on Blog
WSL issues or tricks I had to search for again and again
ping: socket: Operation not permitted Temporary failure in name resolution
resolv.conf
https://github.com/microsoft/WSL/issues/6404#issuecomment-810538101
It seems lounching VSCode daemon messes things up Setup below helped me, thanks guys: /etc/wsl.conf [network] generateResolvConf = false Shutdown wsl wsl --shutdown Start wsl, delete /etc/resolv.conf symbolic link and create a file instead: /etc/resolv.conf nameserver 8.8.8.8
It seems lounching VSCode daemon messes things up
Setup below helped me, thanks guys:
[network] generateResolvConf = false
wsl --shutdown
nameserver 8.8.8.8
But this solution ruins mDNS.
If the DNS works after disabling Firewall, try allowing 172.16.0.0/12 inbound in Windows Defender.
172.16.0.0/12
https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
https://hungyi.net/posts/wsl2-reserved-ports/
Run netsh int ipv4 show excludedportrange protocol=tcp to show reserved ports.
netsh int ipv4 show excludedportrange protocol=tcp
netsh int ipv4 set dynamic tcp start=51001 num=5000
reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f
View Post on Blog
No Network
Solution 1:
resolv.conf
https://github.com/microsoft/WSL/issues/6404#issuecomment-810538101
But this solution ruins mDNS.
Solution 2: Check Firewall
If the DNS works after disabling Firewall, try allowing
172.16.0.0/12
inbound in Windows Defender.Run Linux GUI apps on the Windows Subsystem for Linux
https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
Hyper-V & Reserved Ports
https://hungyi.net/posts/wsl2-reserved-ports/
Run
netsh int ipv4 show excludedportrange protocol=tcp
to show reserved ports.netsh int ipv4 set dynamic tcp start=51001 num=5000
to reset the dynamic port range.reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f
to disable the HNS port exclusion behavior.