wireguard: rename server to local (#167)

source/manual/how-tos/wireguard-client-azire.rst

@@ -33,7 +33,7 @@ favorite text editor.
 Step 2 - Setup WireGuard Instance
 ----------------------------------
 
-Go to tab **Server** and create a new instance. Give it a **Name** and set a desired **Listen Port**. 
+Go to tab **Local** and create a new instance. Give it a **Name** and set a desired **Listen Port**. 
 If you have more than one server instance be aware that you can use the **Listen Port** only once. In 
 the field **Private Key** insert the value from your text file and leave **Public Key** empty. **DNS** 
 and **Tunnel Address** has also to be taken from the configuration. Hit **Save** and go to **Endpoint** 
@@ -42,7 +42,7 @@ tab.
 On **Endpoint** tab create a new Endpoint, give it a **Name**, set 0.0.0.0/0 in **Tunnel Address** and set
 the DNS name from your configuration in **Endpoint Address**. Don't forget to do this also for the port.
 
-Go back to tab **Server**, open the instance and choose the newly created endpoint in **Peers**.
+Go back to tab **Local**, open the instance and choose the newly created endpoint in **Peers**.
 
 Now we can **Enable** the VPN in tab **General** and continue with the setup.
 

source/manual/how-tos/wireguard-client-mullvad.rst

@@ -17,7 +17,7 @@ you have read the basic howto :doc:`wireguard-client`.
 Step 1 - Setup WireGuard Instance
 ----------------------------------
 
-Go to tab **Server** and create a new instance. Give it a **Name** and set a desired **Listen Port**. 
+Go to tab **Local** and create a new instance. Give it a **Name** and set a desired **Listen Port**. 
 If you have more than one server instance be aware that you can use the **Listen Port** only once. In 
 the field **Tunnel Address** insert an unsused private IP address and subnet mask. We don't need it in
 the first step, but as it is required we can't go on without it. Every other field can be left blank.
@@ -26,7 +26,7 @@ Hit **Save** and open your instance again to write down your public key. You nee
 of the configuration from the Mullvad API servers. 
 
 Now change to your OPNsense CLI via SSH or Console and execute the curl string below. Please replace the
-**account** data with your own ID you got from MullvadVPN and **pubkey** with the one in your **Server**
+**account** data with your own ID you got from MullvadVPN and **pubkey** with the one in your **Local**
 
 .. code-block:: sh
 
@@ -43,7 +43,7 @@ public key and set it as **Public Key**. Also don't forget **Endpoint Address**
 
 .. _list: https://www.mullvad.net/en/servers/#wireguard
 
-Go back to tab **Server**, open the instance and choose the newly created endpoint in **Peers**.
+Go back to tab **Local**, open the instance and choose the newly created endpoint in **Peers**.
 
 Now we can **Enable** the VPN in tab **General** and continue with the setup.
 

source/manual/how-tos/wireguard-client.rst

@@ -27,8 +27,8 @@ via :menuselection:`VPN --> WireGuard`.
 Step 2a - Setup WireGuard Server
 --------------------------------
 
-The setup of a central VPN server is very simple. Just go to tab **Server** and create a new instance.
-Give it a **Name** and set a desired **Listen Port**. If you have more than one server instance be 
+The setup of a central VPN server is very simple. Just go to tab **Local** and create a new instance.
+Give it a **Name** and set a desired **Listen Port**. If you have more than one service instance be 
 aware that you can use the **Listen Port** only once. For **Tunnel Address** choose an unused network
 to tunnel all clients just like with OpenVPN or GRE (e.g. 192.168.0.1/24).
 **Peers** can not be chosen yet since we have not created them yet. 
@@ -39,7 +39,7 @@ Now go to tab **Endpoints** and add the fist road warrior, give it a **Name**, i
 Key** and the **Tunnel Address** (e.g. 192.168.0.2/24). **Endpoint Address** and  **Endpoint Port**
 can be left empty since they are mostly dynamic, now hit **Save changes**.
 
-Go back to tab **Server**, open the instance and choose the newly created endpoint in **Peers**.
+Go back to tab **Local**, open the instance and choose the newly created endpoint in **Peers**.
 
 Now we can **Enable** the VPN in tab **General** and continue with the setup.
 
@@ -88,7 +88,7 @@ the creation of a new instance. Then networks which should be routed via WireGua
 added to your **Tunnel Address** in the endpoint configuration of your client (e.g. 192.168.0.0/24 
 when this is the LAN of WireGuard server). For pushing all network traffic via VPN you can add 
 0.0.0.0/0. If you do this it's important to also specifiy a DNS server which will be added to your
-interface. Therefore go to **Server**, edit your instance and fill in one or more IP addresses to 
+interface. Therefore go to **Local**, edit your instance and fill in one or more IP addresses to 
 the **DNS** field. 
 
 

source/manual/how-tos/wireguard-s2s.rst

@@ -29,8 +29,8 @@ via :menuselection:`VPN --> WireGuard`.
 Step 2 - Setup WireGuard
 ------------------------
 
-The setup of a Site-2-Site VPN is very simple. Just go to tab **Server** and create a new instance.
-Give it a **Name** and set a desired **Listen Port**. If you have more than one server instance be 
+The setup of a Site-2-Site VPN is very simple. Just go to tab **Local** and create a new instance.
+Give it a **Name** and set a desired **Listen Port**. If you have more than one service instance be 
 aware that you can use the **Listen Port** only once. For **Tunnel Address** choose a new virtual 
 network to run communication over it, just like with OpenVPN or GRE (e.g. 192.168.0.1/24).
 **Peers** can not be chosen yet since we have not created them yet. 
@@ -42,7 +42,7 @@ keys. Now go to tab **Endpoints** and add the remote site, give it a **Name**, i
 Key** and the **Tunnel Address** (e.g. 192.168.0.2/24). **Endpoint Address** is the public IP of the
 remote site and you can also set optionally the **Endpoint Port**, now hit **Save changes**.
 
-Go back to tab **Server**, open the instance and choose the newly created endpoint in **Peers**.
+Go back to tab **Local**, open the instance and choose the newly created endpoint in **Peers**.
 
 Now we can **Enable** the VPN in tab **General** and go on with the setup.