Skip to content
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

Troubleshooting section incorrect: "Bash loses network connectivity once connected to a VPN" #978

Closed
thernstig opened this issue Oct 31, 2020 · 3 comments

Comments

@thernstig
Copy link

The section "Bash loses network connectivity once connected to a VPN" (https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#bash-loses-network-connectivity-once-connected-to-a-vpn) seems outdated.

Problem 1
5a says:

Delete the first line from the file, which says "# This file was automatically generated by WSL. To stop automatic generation of this file, remove this line.".

However, looking inside /etc/resolv.conf it reads:

This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
[network]
generateResolvConf = false

Problem 2
I actuall tried both to remove the line, and to add this to my /etc/wsl.conf (only thing I have in there):

[network]
generateResolvConf = false

but neither worked. The /etc/resolv.conf is updated once I exit/enter Ubuntu WSL2 again. Is problem 2 a documentation issue, or a real problem? For reference, my /etc/wsl.conf has permission 644.

@craigloewen-msft
Copy link
Collaborator

This is a known issue that we're working on, tracked here: microsoft/WSL#8030

@thernstig
Copy link
Author

@craigloewen-msft when that is solved, will the docs problems described above then be correct?

@craigloewen-msft
Copy link
Collaborator

Oh great call out! I've updated the docs to be more accurate in this commit.
4b39680

Thank you for the suggestion!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants