From 48cdc53bc951609b2e35aa4350550ba259578ea7 Mon Sep 17 00:00:00 2001 From: Jack Ivanov Date: Thu, 9 May 2019 16:47:31 +0200 Subject: [PATCH] Update docs --- docs/client-linux-wireguard.md | 6 +++--- docs/faq.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/client-linux-wireguard.md b/docs/client-linux-wireguard.md index 52f6e85a..cc00807f 100644 --- a/docs/client-linux-wireguard.md +++ b/docs/client-linux-wireguard.md @@ -9,7 +9,7 @@ To connect to your AlgoVPN using [WireGuard](https://www.wireguard.com) from Ubu sudo add-apt-repository ppa:wireguard/wireguard # Update the list of available packages (not necessary on Bionic or later): -sudo apt update +sudo apt update # Install the tools and kernel module: sudo apt install wireguard @@ -27,9 +27,9 @@ The Algo-generated config files for WireGuard are named `configs//wi If your client is running Bionic (or another Linux that uses `systemd-resolved` for DNS but does not have `resolvectl` or `resolvconf` installed) you should first edit the config file. Comment out the line that begins with `DNS =` and replace it with: ``` -PostUp = systemd-resolve -i %i --set-dns=172.16.0.1 --set-domain=~. +PostUp = systemd-resolve -i %i --set-dns= --set-domain=~. ``` -Use the IP address shown on the `DNS =` line (for most, this will be `172.16.0.1`). If the `DNS =` line contains multiple IP addresses, use multiple `--set-dns=` options. +Use the IP address shown on the `DNS =` line (it's randomly generated for each deployment). If the `DNS =` line contains multiple IP addresses, use multiple `--set-dns=` options. ### Ubuntu 18.10 (Cosmic) or 19.04 (Disco) diff --git a/docs/faq.md b/docs/faq.md index 16a69b32..5e59b63f 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -50,7 +50,7 @@ Algo is short for "Al Gore", the **V**ice **P**resident of **N**etworks everywhe ## Can DNS filtering be disabled? -You can temporarily disable DNS filtering for all IPsec clients at once with the following workaround: SSH to your Algo server (using the 'shell access' command printed upon a successful deployment), edit `/etc/ipsec.conf`, and change `rightdns=172.16.0.1` to `rightdns=8.8.8.8`. Then run `sudo systemctl restart strongswan`. DNS filtering for Wireguard clients has to be disabled on each client device separately by modifying the settings in the app, or by directly modifying the `DNS` setting on the `clientname.conf` file. If all else fails, we recommend deploying a new Algo server without the adblocking feature enabled. +You can temporarily disable DNS filtering for all IPsec clients at once with the following workaround: SSH to your Algo server (using the 'shell access' command printed upon a successful deployment), edit `/etc/ipsec.conf`, and change `rightdns=` to `rightdns=8.8.8.8`. Then run `sudo systemctl restart strongswan`. DNS filtering for Wireguard clients has to be disabled on each client device separately by modifying the settings in the app, or by directly modifying the `DNS` setting on the `clientname.conf` file. If all else fails, we recommend deploying a new Algo server without the adblocking feature enabled. ## Wasn't IPSEC backdoored by the US government?