From f5ccbdf9d35f4e2bb08b9a62375655004a207d56 Mon Sep 17 00:00:00 2001 From: Donald Zou Date: Mon, 15 Dec 2025 17:13:46 +0800 Subject: [PATCH] Fixed Restricted Peer might still appear after restricted --- src/modules/WireguardConfiguration.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/modules/WireguardConfiguration.py b/src/modules/WireguardConfiguration.py index f1fdfe16..0c075806 100644 --- a/src/modules/WireguardConfiguration.py +++ b/src/modules/WireguardConfiguration.py @@ -404,6 +404,7 @@ class WireguardConfiguration: try: if "[Peer]" not in content: current_app.logger.info(f"{self.Name} config has no [Peer] section") + self.Peers = [] return peerStarts = content.index("[Peer]") @@ -477,6 +478,7 @@ class WireguardConfiguration: with self.engine.connect() as conn: existingPeers = conn.execute(self.peersTable.select()).mappings().fetchall() for i in existingPeers: + print(i) tmpList.append(Peer(i, self)) self.Peers = tmpList @@ -665,9 +667,8 @@ class WireguardConfiguration: if not self.__wgSave(): return False, "Failed to save configuration through WireGuard" - + self.getRestrictedPeers() self.getPeers() - if numOfRestrictedPeers == len(listOfPublicKeys): return True, f"Restricted {numOfRestrictedPeers} peer(s)" return False, f"Restricted {numOfRestrictedPeers} peer(s) successfully. Failed to restrict {numOfFailedToRestrictPeers} peer(s)"