-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GITBOOK-192: change request with no subject merged in GitBook
- Loading branch information
1 parent
b4da408
commit 1e1e4b8
Showing
9 changed files
with
80 additions
and
14 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
65 changes: 65 additions & 0 deletions
65
tutorials/step-by-step-setting-up-a-vpn-server/adding-additional-vpn-locations.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
--- | ||
description: >- | ||
If you have used our one-line install setup (for example described in this | ||
tutorial) | ||
--- | ||
|
||
# Adding additional VPN locations | ||
|
||
If you have used our one-line install setup (for example [described in this tutorial](./)) one VPN location (one gateway instance) is done automatically. | ||
|
||
There is often a need to launch additional locations (e.g. to separate groups of users or clients), to do this you need to add another location (and launch another gateway controlling this location). | ||
|
||
Here is a step-by-step way to do so: | ||
|
||
### Adding a new Location | ||
|
||
In defguard interface in VPN Location please click: **Edit location settings** (button in the top right corner): | ||
|
||
<figure><img src="../../.gitbook/assets/Screenshot 2024-08-15 at 21.40.38.png" alt=""><figcaption></figcaption></figure> | ||
|
||
Then _**Add new location**_ and configure the new VPN location. | ||
|
||
{% hint style="warning" %} | ||
Rember that the: | ||
|
||
* VPN IP address needs to be different then in the first location | ||
* Gateway address should be the same (same public IP) | ||
* Gateway port **must be different** | ||
{% endhint %} | ||
|
||
After configuring the location, please: | ||
|
||
* copy the gateway token | ||
* and note that the gateway is disconnected | ||
|
||
<figure><img src="../../.gitbook/assets/Screenshot 2024-08-15 at 21.28.25.png" alt=""><figcaption></figcaption></figure> | ||
|
||
### Adding new gateway in docker | ||
|
||
Now go to the server and open the docker-compose.yml file, and scroll to the gateway section, it should look like this: | ||
|
||
<figure><img src="../../.gitbook/assets/docker-gw1.png" alt=""><figcaption></figcaption></figure> | ||
|
||
Now copy the **whole gateway section and:** | ||
|
||
* **name it in a uniqe way,** eg. _gateway-customer2_  | ||
* in the enviroment variable `DEFGUARD_TOKEN`: add the token you have copied from the new location, like so: | ||
|
||
<figure><img src="../../.gitbook/assets/Screenshot 2024-08-15 at 21.52.19.png" alt=""><figcaption></figcaption></figure> | ||
|
||
Now you need to launch the new gateway, just by the following command: | ||
|
||
``` | ||
docker compose up -d gateway-customer2 | ||
``` | ||
|
||
<figure><img src="../../.gitbook/assets/Screenshot 2024-08-15 at 21.54.02.png" alt=""><figcaption></figcaption></figure> | ||
|
||
Now if you go back to the location settings you will see **instantly that the new gateway has connected for that location:** | ||
|
||
|
||
|
||
<figure><img src="../../.gitbook/assets/Screenshot 2024-08-15 at 21.29.37.png" alt=""><figcaption></figcaption></figure> | ||
|
||
And that's it, you have a new VPN location ready. |