manual: fixing parsing #70
@ -69,19 +69,19 @@ To set the WireGuard connection on Linux or MAC, create a WireGuard configuratio
|
|||||||
|
|
||||||
* Copy the content **WireGuard Config** from the Dashboard **Details** window
|
* Copy the content **WireGuard Config** from the Dashboard **Details** window
|
||||||
* Paste the content to a file with the extension `.conf` (e.g. **wg.conf**) in the directory `/etc/wireguard`
|
* Paste the content to a file with the extension `.conf` (e.g. **wg.conf**) in the directory `/etc/wireguard`
|
||||||
* ```
|
```
|
||||||
sudo nano /etc/wireguard/wg.conf
|
sudo nano /etc/wireguard/wg.conf
|
||||||
```
|
```
|
||||||
* Start WireGuard with the command **wg-quick** and, as a parameter, pass the configuration file without the extension (e.g. *wg.conf -> wg*)
|
* Start WireGuard with the command **wg-quick** and, as a parameter, pass the configuration file without the extension (e.g. *wg.conf -> wg*)
|
||||||
* ```
|
```
|
||||||
wg-quick up wg
|
wg-quick up wg
|
||||||
```
|
```
|
||||||
* Note that you can also specify a config file by path, stored in any location
|
* Note that you can also specify a config file by path, stored in any location
|
||||||
* ```
|
```
|
||||||
wg-quick up /etc/wireguard/wg.conf
|
wg-quick up /etc/wireguard/wg.conf
|
||||||
```
|
```
|
||||||
* If you want to stop the WireGuard service, you can write the following in the terminal
|
* If you want to stop the WireGuard service, you can write the following in the terminal
|
||||||
* ```
|
```
|
||||||
wg-quick down wg
|
wg-quick down wg
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -105,7 +105,7 @@ To set the WireGuard connection on Windows, add and activate a tunnel with the W
|
|||||||
As a test, you can [ping](../../computer_it_basics/cli_scripts_basics.md#test-the-network-connectivity-of-a-domain-or-an-ip-address-with-ping) the virtual IP address of the VM to make sure the WireGuard connection is properly established. Make sure to replace `VM_WireGuard_IP` with the proper WireGuard IP address:
|
As a test, you can [ping](../../computer_it_basics/cli_scripts_basics.md#test-the-network-connectivity-of-a-domain-or-an-ip-address-with-ping) the virtual IP address of the VM to make sure the WireGuard connection is properly established. Make sure to replace `VM_WireGuard_IP` with the proper WireGuard IP address:
|
||||||
|
|
||||||
* Ping the deployment
|
* Ping the deployment
|
||||||
* ```
|
```
|
||||||
ping VM_WireGuard_IP
|
ping VM_WireGuard_IP
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -116,7 +116,7 @@ As a test, you can [ping](../../computer_it_basics/cli_scripts_basics.md#test-th
|
|||||||
To SSH into the deployment with Wireguard, use the **WireGuard IP** shown in the Dashboard **Details** window.
|
To SSH into the deployment with Wireguard, use the **WireGuard IP** shown in the Dashboard **Details** window.
|
||||||
|
|
||||||
* SSH into the deployment
|
* SSH into the deployment
|
||||||
* ```
|
```
|
||||||
ssh root@VM_WireGuard_IP
|
ssh root@VM_WireGuard_IP
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user