From: Tobias Brunner <tobias@strongswan.org>
Date: Fri, 12 Apr 2024 12:01:23 +0000 (+0200)
Subject: swanctl: Document possibility of non-zero base addresses for in-memory pools
X-Git-Tag: android-2.5.2~29
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=afeac365fd0a29cbdda312284df0ea877ad1c886;p=thirdparty%2Fstrongswan.git

swanctl: Document possibility of non-zero base addresses for in-memory pools

References strongswan/strongswan#2205
---

diff --git a/src/swanctl/swanctl.opt b/src/swanctl/swanctl.opt
index d9fd949ed1..78256a6af2 100644
--- a/src/swanctl/swanctl.opt
+++ b/src/swanctl/swanctl.opt
@@ -1331,7 +1331,10 @@ pools.<name>.addrs =
 
 	Subnet or range defining addresses allocated in pool. Accepts a single CIDR
 	subnet defining the pool to allocate addresses from or an address range
-	(<from>-<to>).  Pools must be unique and non-overlapping.
+	(<from>-<to>). If the address in CIDR notation is not the network ID of the
+	subnet (e.g. 10.1.0.5/24 instead of 10.1.0.0/24), addresses below it won't
+	be allocated to clients (they could e.g. be assigned manually to internal
+	hosts like the VPN server itself). Pools must be unique and non-overlapping.
 
 pools.<name>.<attr> =
 	Comma separated list of additional attributes from type <attr>.