AppGate ZTNA assigns each authenticated client an internal IP address. This address is used by the virtual tunnel interface for client-to-Gateway communication.
AppGate ZTNA includes default IP pools for both IPv4 and IPv6. The tunnel type matches the traffic type: IPv4 traffic always uses the IPv4 tunnel, and IPv6 traffic uses the IPv6 tunnel.
To support all concurrent users, verify that your IP pool size is sufficient. You may need to create a new IP pool or extend an existing one.
For more information about how tunneled traffic is handled in AppGate ZTNA, see Routing client traffic.
See Configuring IP pools to add an IP pool.
IP pools in the AppGate ZTNA system
IP pools provide two types of address for devices: a tunnel IP address, and an alternative mapped tunnel IP address presented on a specific Site.
Tunnel IP address
The Controller uses the IP pool to assign a unique internal IP address to each tunnel adapter on client devices. To assign different IP pools to specific user groups, link a named IP pool to an identity provider. See Identity Providers for more information.
IP pool mapping
IP pools are also used when configuring mapped IP addresses.
The client IP address visible on the protected network comes from the IP pool (based on IdP settings) and is the same on all Sites. IP pool mappings are useful when Disable Source NAT on Gateways is enabled and clients connect to more than one WAN-connected Site. When a single tunnel IP address is presented on all Sites, routing issues can occur because the same tunnel IP is announced from two or more Gateways on different Sites that share the same network or WAN.
To mitigate this problem, AppGate ZTNA provides the IP pool mapping feature, which lets the client present a source address from a different IP pool on a specific Site. You can expand this to as many Sites as your environment requires
This feature ensures that replies to the client—such as during a VoIP call—are routable on the network or WAN. You can also use geo-claims to optimize routing by switching the active entitlement between Sites based on the user or device location.
Mapping options
IP pool mapping supports two methods, depending on your use case: Translation and Allocation.

For example, a user connects to AppGate ZTNA with a policy that includes access to resources on two WAN connected Sites (DC1 and DC2).
Translation: use this method when you have smaller IP pools (/24) and your entire user community uses the mapped Site. The mapped IP pool range must be identical to the original, because the IP address is translated to the same position in the new range.
Tunnel pool for all users = 192.168.100.0/24
Site mapping pool for DC1 AppGate ZTNA Site = 10.1.1.0/24
Site mapping pool for DC2 AppGate ZTNA Site = 10.2.2.0/24
When traffic reaches DC1, the AppGate ZTNA Gateway maps the assigned tunnel IP address 192.168.100.50 to the corresponding address 10.1.1.50 in the DC1 mapped pool. The Gateway NATs return traffic back to the original tunnel IP 192.168.100.50. Traffic reaching DC2 appears on the network as 10.2.2.50, and return traffic is NATed back to 192.168.100.50.return back the tun IP 192.168.100.50.
Allocation: use this method when you have larger IP pools (/16) and only a small portion of your user community uses the mapped Site. The mapped IP pool range must be large enough for the number of users on that Site.
Tunnel pool for all users = 192.168.100.0/20
Site mapping pool for DC1 AppGate ZTNA Site = 10.1.1.0/26
Site mapping pool for DC2 AppGate ZTNA Site = 10.2.2.0/26
When traffic reaches DC1, the AppGate ZTNA Gateway maps the tunnel IP address 192.168.100.50 to the next available address—10.1.1.13—on a first-come, first-served basis. The next user receives 10.1.1.14. The Gateway NATs return traffic back to tunnel IP 192.168.100.50. Traffic reaching DC2 appears on the network as 10.2.2.17, and return traffic is NATed back to 192.168.100.50.
NOTE
This feature still supports optimal high availability at each Site by moving the mapped tunnel IP to another healthy Gateway.
IP pool address assignment in AppGate ZTNA
The following terms describe IP address assignment:
Current. The IP address is included in a device's entitlement token for its lifetime (maximum 7 days); it may be in active use until the token expires.
Leased. The IP address is reserved for the device for a period of X days after the entitlement token expires.
Associated. The IP address remains linked to the device.
When the Controller issues an entitlement token, the assigned IP address is reported as current until the token expires—which may be well after the user signs out.
When the entitlement token expires and the IP address is no longer in active use, the address remains leased for the lease period (default: 30 days). This ensures the same IP address is reassigned to the same device the next time it connects, improving user experience and keeping audit logs consistent. You can configure the lease time for each pool.
When the lease time expires, the IP address remains associated to that device. It will always be reassigned to that device as long as it has not been reassigned to another device in the meantime. Associated IP addresses are reassigned to new devices when there are no new IP addresses in the pool. Any existing association is then lost.
IP pool size
System configuration and networking can significantly affect the required IP pool size. Consider the following before deploying AppGate ZTNA:
The default IPv4 and IPv6 ranges allow for only 254 addresses out of the box.
Every device that connects will be assigned its own IP address from the pool. If every user has a desktop and mobile phone, then the IP pools should be set to
. This becomes more complicated if users have virtual desktops. In this case, those users may connect from a brand new device each time, consuming a new IP address. In such cases the IP range must be much bigger and/or the lease time reduced accordingly. If multiple identity providers are configured, AppGate ZTNA treats each IdP sign-in as a different user, even when the same user signs in on the same device. Each time a user connects through a different IdP, a new IP address is consumed
When using HA Controllers, allow for sufficient IP addresses for all new users in case one of the Controllers becomes unavailable. The IP pool is split between Controllers equally when assigning new IP addresses. However, existing (current, leased, and associated) IP addresses can be renewed by any Controller. As a result, the available address range for new users will be degraded for a period of time. The sizing of the pool should be increased to allow for this (which depends on how long a Controller might be unavailable). We recommend a minimum of
and a maximum of . When Gateway SNAT is in use, the IP pool is still required for traffic between the client and the Gateway, even though the Gateway address is used on the network.
For the IP pool mapping translation feature, the pool size must exactly match the original IP pool size.
For the IP pool mapping allocation feature, the pool size must be adequate for the number of users on that Site.
If you need more IP addresses:
Every IP pool can include multiple ranges, so you can add another range using IP pools.
You can keep entitlement token lifetimes short. This will move any IP addresses from current to leased for signed out users.
Reducing the lease time moves IP addresses from leased to associated, allowing them to be re-assigned..
NOTE
You cannot delete or change an existing range within an IP pool, but you can add new ranges and range exclusions.
Monitoring IP pool usage
The following tools monitor IP pool address assignment and use:
The IP Pools page (Identity > IP Pools) provides statistics on currently used and leased IPs.
Metrics report on current, leased, and total usage for each IP pool.
When any pool's currently used and leased IP addresses reach 75% of the total size, a healthcheck warning is issued.
You can see an individual user's IP address and mapped IP addresses from the Session Details on the Dashboard.
You can see an individual user's IP address in the About screen on the client.
Using IPv6
You do not need a public IPv6 network to pass IPv6 application traffic. However, the following elements must be in place:
Hosts must have an IPv6 address on an IPv6-enabled network behind the Gateways.
The DNS server specified must resolve protected hosts to an IPv6 address.
There must be an AppGate ZTNA IPv6 tunnel that requires:
A defined IPv6 pool
Enabling IPv6 if using the DNS resolver
Specifying the IPv6 pool in the identity provider

If you are not using IPv6
If an IPv6 pool is not present, then IPv6 is disabled on the Gateways’ network tunnel devices. This has two advantages:
Setting up both IPv4 and IPv6 tunnel devices on the Gateways is slower, so disabling IPv6 reduces session setup time.
In many situations—especially with DNS—having IPv6 configured can cause slow or failed connections.
Because all new Collectives include a default IPv6 pool, this check has no immediate benefit. Remove the default IPv6 pool if your Collective does not require IPv6.