Skip to content

Commit

Permalink
improve docs
Browse files Browse the repository at this point in the history
  • Loading branch information
Jacob Halsey committed Aug 9, 2023
1 parent b533afe commit cd47776
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 6 deletions.
2 changes: 1 addition & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 6 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,15 @@ Thanks to @pyther for the [inspiration for this tool](https://gist.github.com/py
**Ensure you have first fixed the route table for WSL2, and not broken the Windows DNS server priority in the process**.
See the [guide](./docs/ROUTING.md) for how to do this.

Simply download `wsl2-dns-agent.exe` from the [releases page](https://github.com/jacob-pro/wsl2-dns-agent/releases/latest)
**Ensure you have the `chattr` command present within your WSL2 distribution**.
For RHEL-family distributions you can use `sudo yum install e2fsprogs`.

Save it to your startup folder (`%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup`).
Download `wsl2-dns-agent.exe` from the [releases page](https://github.com/jacob-pro/wsl2-dns-agent/releases/latest)

Launch the application.
(Optionally) save it to your [startup folder](https://support.microsoft.com/en-us/windows/add-an-app-to-run-automatically-at-startup-in-windows-10-150da165-dcd9-7230-517b-cf3c295d89dd)
(`%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup`), so it is automatically launched when you log in.

Note: You must have the `chattr` command installed within your WSL2 distribution.
Launch the `wsl2-dns-agent.exe` application.

## Diagnostics

Expand Down
2 changes: 1 addition & 1 deletion docs/ROUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ This guide applies to Cisco AnyConnect in environments where it has been configu
## Step #1 - WSL2 Internet Access

First you need to ensure your WSL2 distributions can access the internet. Before connecting to the VPN your routes for
WSL2 will look something like (using the `Get-NetAdapter` command in powershell):
WSL2 will look something like (using the `Get-NetRoute` command in powershell):

```
ifIndex DestinationPrefix NextHop RouteMetric ifMetric PolicyStore
Expand Down

0 comments on commit cd47776

Please sign in to comment.