From a829cce278c90f47ba2fc13409cf40a633c22657 Mon Sep 17 00:00:00 2001
From: coja <coja@dmz.rs>
Date: Wed, 26 Mar 2025 05:04:30 +0100
Subject: [PATCH] [Readme] update

Signed-off-by: coja <coja@dmz.rs>
---
 kralizec/wireguard11/README.md | 26 ++++++++++++--------------
 1 file changed, 12 insertions(+), 14 deletions(-)

diff --git a/kralizec/wireguard11/README.md b/kralizec/wireguard11/README.md
index 52d5c3c..93a93b4 100644
--- a/kralizec/wireguard11/README.md
+++ b/kralizec/wireguard11/README.md
@@ -8,19 +8,6 @@ Check dmzadmin for `wireguard.gpg` to know who to contact for access
 
 ---
 
-### Server config
-
-New user/client needs to provide their wireguard `publickey` and new ip on the network needs to be assigned (`x`)
-add next lines to the bottom of the conf file - `/etc/wireguard/wg0.conf`
-
-```conf
-[Peer]
-PublicKey = <client_public_key>
-AllowedIPs = 192.168.164.x/32
-```
-
----
-
 ### Client config
 
 client conf example
@@ -47,7 +34,18 @@ PersistentKeepalive = 21
 
 ---
 
-Command to resolve ip clashing with current and wireguard network 
+### Server config
+
+New user/client needs to provide their wireguard `publickey` and new ip on the network needs to be assigned (`x`)
+check the server conf file `/etc/wireguard/wg0.conf` to find free address
+
+```sh
+sudo wg set wg0 peer <client_public_key> allowed-ips 192.168.164.x/32
+```
+
+---
+
+Command to resolve ip clashing with current and wireguard network, if needed
 
 ```shell
 ip route add <ip> dev <wg0>