Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| omv7:omv7_plugins:wireguard [2024/02/17 17:35] – [Configuring a Client] chente | omv7:omv7_plugins:wireguard [2024/04/24 15:28] (current) – [Configuring a Client] chente | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{indexmenu_n> | ||
| \\ | \\ | ||
| < | < | ||
| Line 19: | Line 20: | ||
| * You will be able to access all your shared folders and all the services you have configured on your local network as if you were there. | * You will be able to access all your shared folders and all the services you have configured on your local network as if you were there. | ||
| * By default all client traffic will be forwarded through the VPN connection (it is configurable), | * By default all client traffic will be forwarded through the VPN connection (it is configurable), | ||
| - | * The Custom Config tab allows you to make configurations according to specific needs. You can implement any Wireguard network topology. | + | * The Custom Config tab allows you to make configurations according to specific needs. You can use this tab if you need to connect the server to an external Wireguard VPN service, or you can implement any Wireguard network topology. |
| * The point-to-point connection allows the connection between two servers, communicating only with each other. For example to make remote backups. | * The point-to-point connection allows the connection between two servers, communicating only with each other. For example to make remote backups. | ||
| * The site-to-site provides a connection between two networks so that any IP on a local network is able to communicate with any IP on another local network. | * The site-to-site provides a connection between two networks so that any IP on a local network is able to communicate with any IP on another local network. | ||
| Line 139: | Line 140: | ||
| * **Name** You can name the client to identify it later. | * **Name** You can name the client to identify it later. | ||
| * **Advanced Configuration** These are custom configuration options that are not necessary to configure a client except for special needs. If you don't need any of this, leave the default values. | * **Advanced Configuration** These are custom configuration options that are not necessary to configure a client except for special needs. If you don't need any of this, leave the default values. | ||
| - | * **Persistent Keepalive** The default setting is to leave it blank. In some cases it may be necessary to set a value here to keep the connection active. A suitable value is usually 25 (Every 25 seconds the client will send a packet to the server). | ||
| * **Persistent Keepalive** The default setting is to leave it blank. In some cases it may be necessary to set a value here to keep the connection active. A suitable value is usually 25 (Every 25 seconds the client will send a packet to the server). | * **Persistent Keepalive** The default setting is to leave it blank. In some cases it may be necessary to set a value here to keep the connection active. A suitable value is usually 25 (Every 25 seconds the client will send a packet to the server). | ||
| * **DNS Servers** The default setting is to leave it blank. In some cases it may be necessary to establish a DNS server for the client to communicate correctly on the local network. The usual thing will be to establish the IP of the router. The menu will show the existing value in resolv.conf in case you want to copy it to the field on the right. | * **DNS Servers** The default setting is to leave it blank. In some cases it may be necessary to establish a DNS server for the client to communicate correctly on the local network. The usual thing will be to establish the IP of the router. The menu will show the existing value in resolv.conf in case you want to copy it to the field on the right. | ||
| - | * **Restrict** button. The default setting is to leave it unchecked, this will set AllowedIPs to '' | + | * **Restrict** button. The default setting is to leave it unchecked, this will set AllowedIPs to '' |
| * **VPN** button. Pressing this button will remove the '' | * **VPN** button. Pressing this button will remove the '' | ||
| * **Local IP** button. Pressing this button will remove the network range '' | * **Local IP** button. Pressing this button will remove the network range '' | ||
| Line 148: | Line 148: | ||
| * Click **Save**. At this point, if you have already activated the tunnel and the client, the connection will be up and running. | * Click **Save**. At this point, if you have already activated the tunnel and the client, the connection will be up and running. | ||
| * By pressing the button **Client Config** you can see the client configuration file, you can copy and paste the text in a file to configure the connection in the client. If you do it this way, add the ending " | * By pressing the button **Client Config** you can see the client configuration file, you can copy and paste the text in a file to configure the connection in the client. If you do it this way, add the ending " | ||
| - | * A QR will appear in the table (if the client is enabled), which you can scan from a smartphone to configure the connection without having to copy a file. If you need to send it you can take a photo. Treat this image as a password, it is the access key to your network. | + | * A QR will appear in the table (if the client is enabled), which you can scan from a smartphone to configure the connection without having to copy a file. If you need to send it you can take a photo. Treat this image as a password, it is the access key to your network |
| * Use a different client configuration for each client. If you configure the same connection on several clients at the same time, they will not be able to connect simultaneously. | * Use a different client configuration for each client. If you configure the same connection on several clients at the same time, they will not be able to connect simultaneously. | ||
| Line 186: | Line 186: | ||
| ---- | ---- | ||
| - | This tab allows you to create a tunnel with the custom settings you need. It allows to open an editing window where you can paste the configuration from a text file, therefore, you can choose the parameters you need for the tunnel. | + | This tab allows you to create a tunnel with the custom settings you need. It allows to open an editing window where you can paste the configuration from a text file, therefore, you can choose the parameters you need for the tunnel. Use this tab if you need to connect the server to an external (commercial) Wireguard VPN service. |
| If you need to configure a tunnel to connect the point-to-point server with another server, or any other network topology, you must do so in this tab, since it allows you to manually define keys, networks and other necessary parameters. | If you need to configure a tunnel to connect the point-to-point server with another server, or any other network topology, you must do so in this tab, since it allows you to manually define keys, networks and other necessary parameters. | ||
| Line 201: | Line 201: | ||
| * In the **Config** field write the configuration content of your tunnel following the Wireguard rules. | * In the **Config** field write the configuration content of your tunnel following the Wireguard rules. | ||
| * You can see how to do it on the [[https:// | * You can see how to do it on the [[https:// | ||
| + | * If you want to connect to a commercial VPN service, they will most likely provide you with the tunnel configuration template. In that case, simply copy and paste that template into the Config field. | ||
| * If you need special topologies you can find them on the [[https:// | * If you need special topologies you can find them on the [[https:// | ||
| * Note that the networks created by the plugin in the **Tunnel** and **Client** tabs are generated in the '' | * Note that the networks created by the plugin in the **Tunnel** and **Client** tabs are generated in the '' | ||