Deploying an Advanced Connector for access from and to unmanaged devices
The Advanced Connector protects remote networks and under‑protected or unmanaged devices by enabling secure, policy‑based connectivity to protected resources through AppGate ZTNA Gateways.
Unlike Express deployment, Advanced mode provides granular configuration options to support complex routing, NAT behavior, and bidirectional traffic flows.
In a typical deployment, the Connector runs as a standalone appliance in a remote location, such as a cloud environment or branch office. It can also be deployed in a high‑availability (HA) configuration.
Key characteristics
Secure access for unmanaged devices in cloud or physical locations
Fine‑grained, policy‑based bi‑directional traffic control
Support for up to 60 resource groups, each handling up to 16,000 TCP connections
Support for up rules (local → protected) and down rules (protected → local)
Optional DHCP relay through connected Gateways
Built‑in Connector identity provider with assigned IPv4 and/or IPv6 pools
Each configured resource group consumes one resource group license.
Basic operation
To configure an Advanced Connector, see Adding a Connector.
A resource group represents a set of local resources that:
Share the same access rights (policy)
Have traffic handled by a single Connector client instance
Each resource group configuration includes:
Name
Local resources
Optional Source NAT and Destination NAT settings
An automatically created Device ID for the Connector client
Each Connector runs multiple headless Linux client instances. Each client:
Is associated with a single resource group
Receives a unique policy
Connects to all available Gateways on the allowed Sites
Runs in an isolated Linux namespace to maintain traffic separation
Each Connector client consumes one IP address from the assigned IP pool (which can be separate from user IP pools). Ensure the pool is large enough to support all configured resource groups.
Connector clients use concealed profiles and credentials and automatically attempt to sign in to the Controller on startup. A valid policy must exist for these clients. Otherwise, repeated sign-in attempts can generate excessive log entries and place unnecessary load on the Controllers.
Resource group IP configuration types
Two IP configuration types are available:
Non-DHCP traffic
Used for standard routed traffic. All NAT and entitlement options are available.
DHCP relay traffic
Used when local resources obtain IP addresses from a remote DHCP server behind a Gateway.
Characteristics:
NAT and SNAT options are not supported
DHCP server details must be specified
Entitlements and policies are generated automatically
Requires a route on the DHCP server (or next hop) pointing the DHCP scope to the AppGate Gateway
Supported only with a single Gateway deployment
Primary use case - Up traffic (local to protected resources)
This use case enables local resources (for example, webcams) to initiate traffic to protected resources.

Up rule flow
A local resource sends traffic to a protected destination.
Traffic is routed to the Connector.
The Connector forwards traffic to the appropriate client based on the resource group.
Traffic is split into tunnels based on entitlements.
Gateway VPN processes enforce entitlement actions.
Traffic is forwarded to protected hosts, using either:
The local resource IP, or
The Gateway IP, depending on NAT configuration
Configuring Up access
Connector configuration
Enable the Connector function on your appliance.
Select the Site to associate with the Connector.
Under Resource Group Configuration, add a new resource group:
Specify a name (for example, webcams)
Define the local resource IP address (for example, 192.168.8.0/25).
Leave Source NAT from Local Resources enabled unless the protected resource must see the original source IP.
If using HA, assign a VIP under High Availability Configuration.
Local resource configuration
Ensure local resources route protected traffic to the Connector by one of the following methods:
Add static routes on the device
Add routes on the local router
Set the Connector as the default gateway and enable Default Gateway (Forward non‑matching traffic)
Cloud‑specific requirements:
Add subnet routes for protected resources via the Connector
Enable IP forwarding:
AWS: Disable Source/Destination Check
Azure: Enable IP forwarding on the NIC

Identity provider
Assign IPv4 and/or IPv6 pools to the built‑in Connector identity provider (for example, 192.168.100.0/24). Default pools can be expanded if required.
Entitlement
Create an entitlement allowing access to the protected resource (for example, TCP to 10.1.2.3:1000). If required, include DNS access to protected DNS servers.
Policy
Create a policy scoped to Connector clients:
Identity Provider = "Connector"
user.clientNamematches the resource name
Add the entitlement to the policy.
Dashboard
Verify the Connector function is healthy on the appliance status dashboard. This confirms the Connector client is signed in and has entitlements assigned.
From Session Details:
Locate the Connector client by name.
Verify allowed entitlement actions.
Check User Claims > ag to confrm the correct
connectorSubnetsare present.
Protected resources
If Source NAT from Local Resources is disabled:
Traffic appears to originate from the local resource IP
The
ag.connectedSubnetsclaim reflects the local resource IPEnsure return routes exist on protected hosts

If Disable Source NAT on Gateways is also enabled, protected hosts see the local resource IP as the source.
Alternative use case - Down traffic (protected resources to local)
This use case enables protected resources to initiate traffic to local resources behind the Connector.

Down rule flow (read from bottom)
Protected hosts send traffic to local resource IPs or Connector tun IPs.
Gateway VPN processes forward traffic to the Connector client.
Connector routes traffic to the local resource using NAT configuration.
Local resources return traffic to the Connector.
Configuring Down access

Connector configuration
Enable the Connector function on the appliance.
Select the Site to associate with the Connector.
Under Resource Group Configuration, add a new resource group:
Specify a name (for example, printerA).
Define the local resource IP address (for example, 192.168.8.10).
Leave Source NAT to Local Resources enabled unless the local resource must see the user’s tun IP.
If deploying an HA configuration, assign a VIP under High Availability Configuration.
Local resource configuration
If Source NAT to Local Resources is disabled, traffic from the Connector appears to originate from the user’s Client tun IP. In this case, ensure return routing is configured:
On the device: add a route for the protected hosts' IPs via the Connector
On the router: add a route for the protected hosts' IPs via the Connector
In cloud Cloud environments (AWS, Azure) additional configuration is typically required:
Add a route on the local subnet for source IPs via the Connector
Allow the Connector NIC to accept traffic not addressed to itself:
In AWS, disable "Source/Destination Check".
In Azure, enable "IP forwarding" on the network interface.
Identity provider
Ensure the built-in Connector identity provider has IPv4 and/or IPv6 IP pools assigned for Connector clients (for example, 192.168.100.0/24). Default pools can be expanded if additional tunnel interfaces are required. See IP pools for details.
Site
Disable Source NAT on Gateways for the Site.
If multiple Gateways exist, ensure the backend network supports ARP.
Entitlements and policy
Create a down entitlement (for example, UDP from 10.1.2.3 on port 500).
Create a policy scoped to the Connector client (
user.clientName).Assign the entitlement to the policy.
Dashboard
Verify the Connector function is healthy on the appliance status dashboard. This confirms the Connector client is signed in and has entitlements assigned.
From Session Details:
Locate the Connector client by name.
Verify allowed entitlement actions.
Check User Claims > ag to confrm the correct
connectorSubnetsare present.
Protected resources
When Destination NAT to Local Resources is enabled:
Users send traffic to the Connector client’s tun IP, not the local resource IP
Each tun IP maps one-to-one with a specific local resource
The Connector performs SNAT toward local resources, making traffic appear to originate from the Connector IP

NOTE
Only one local resource can be specified per resource group (one IPv4 and one IPv6).
SSH access to a Connector
SSH access to a Connector without a fixed or public IP address requires a specific configuration. Refer to SSH command line access for details.