From a134cafc88830b757f79b0d4b689788b2da4227c Mon Sep 17 00:00:00 2001 From: Silejonu <48565914+Silejonu@users.noreply.github.com> Date: Wed, 14 Feb 2024 09:08:13 +0100 Subject: [PATCH] Update wireguard-client.rst (#538) Fix mixing up of "PrivateKey" and "PublicKey" in the Step 7 paragraph, in regards to the Appendix --- source/manual/how-tos/wireguard-client.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/manual/how-tos/wireguard-client.rst b/source/manual/how-tos/wireguard-client.rst index 382efa33..48b70566 100644 --- a/source/manual/how-tos/wireguard-client.rst +++ b/source/manual/how-tos/wireguard-client.rst @@ -270,7 +270,7 @@ Client configuration is largely beyond the scope of this how-to since there is s ====================== ==================================================================================================== **[Interface]** **Address** *Refers to the IP(s) specified as Allowed IPs in the Peer configuration on OPNsense. For example, 10.10.10.2/32* - **PublicKey** *Refers to the public key that (along with a private key) needs to be manually or automatically generated on the client. The public key must then be copied into the Peer configuration on OPNsense for the relevant client peer - see Step 3* + **PrivateKey** *Refers to the private key that (along with a public key) needs to be manually or automatically generated on the client. The corresponding public key must then be copied into the Peer configuration on OPNsense for the relevant client peer - see Step 3* **DNS** *Refers to the DNS servers that the client should use for the tunnel - see note below* **[Peer]**