Since then I stopped using netsh port forwards to WSLsince it seems like now it's implicit? (I dunno, I can run a service on WSL as long as that port doesn't collide with something on Windows, and the firewall port is open, my network can use it without me doing the forward. <- restarting WSL and re-doing the port forwards was the fix. I think I had one time Hyper-V decided to change the ip range on the vm network and I was chasing my tail with why a netsh port forward wasn't working. Like if the system goes to sleep/hibernate sometimes my remote vscodes disconnect (the wsl$ share goes offline) but not always, and usually comes back within a minute (but not always) I use WSL2 with the g update for work, use the default behavior, no customization and It's fine.īut on occasion, I have random problems that I don't think are related to WSL2. Omg, this script worked, thank you very very much need to rm /etc/nf to remove the symbol link, this step is very easy to forget.some document says need to wsl -shutdown for the option to take effect.need to /etc/wsl.conf, the document is clear, so it's ok.So (my guess), there is a delete statement that deletes blinding without checking the generateResolvConf = false option.īut despite the current bug, I still think this whole process needs some design, at least more clear document in /etc/nf The real bug here is that the /etc/nf file got deleted when generateResolvConf = false. # this i will prevent delete of the file # for some reason it always delete the /etc/nf when generateResolvConf = false # this is the real bug in wsl GUI version reported here # /etc/nf is a symbol link, delete it to create a regular file # for me, it works without it, keep it here for reference # some document says need restart the wsl once for the configure to work # or manually edit if you have other config in wsl.conf PS C:\WINDOWS\system32> sudo cat /etc/nfĬat: /etc/nf: No such file or add config to /etc/wsl.conf password for cat /etc/nfĬat: /etc/nf: No such file or touch echo 'nameserver 1.1.1.1' > cat /etc/nf Install the latest PowerShell for new features and improvements! Actual behaviorĪctually my nf is being forcefully removed - which IS making WSLg unusable until a new one has been put in place.Ĭopyright (C) Microsoft Corporation. As it did in the WSL (pre-g release) version. The wsl logs reveal nothing about nf Expected behaviorĮxpected is that MY nf is left alone. Start WSL Ubuntu 20.04 session again, and check for the /etc/nf. GenerateResolvConf = sure you have your own sudo rm -f nf
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |