--- title: "Advanced Connector" slug: "connector-advanced-v7-0" description: "Securely connect unmanaged devices with the Advanced Connector, enabling policy-based access and bi-directional traffic control for remote networks." tags: ["Connector (Advanced)", "Connector"] updated: 2026-10-05T18:38:43Z published: 2026-10-05T18:38:43Z canonical: "support.appgate.com/connector-advanced-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Advanced Connector ## 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](/v1/docs/adding-a-connector-v7-0). 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. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/Primary_use_case_up_traffic.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=o2wi6UjRH2VkQab6RB%2FrhdFxCmKKkER3UFktKDeYGV8%3D) #### Up rule flow 1. A local resource sends traffic to a protected destination. 2. Traffic is routed to the Connector. 3. The Connector forwards traffic to the appropriate client based on the resource group. 4. Traffic is split into tunnels based on entitlements. 5. Gateway VPN processes enforce entitlement actions. 6. Traffic is forwarded to protected hosts, using either: - The local resource IP, or - The Gateway IP, depending on NAT configuration ### Configuring Up access #### ![Diagram illustrating IP routing from local resources to protected resources through a Gateway.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/configure_up_access.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=8T%2B17cENWxsYMWGhCPkNmTIn%2B9d41Cw69VGDhlKC3%2Fo%3D) Connector configuration 1. Enable the [Connector function](/v1/docs/adding-a-connector-v7-0) on your appliance. 2. Select the Site to associate with the Connector. 3. 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. 4. If using HA, assign a VIP under [High Availability Configuration](/v1/docs/adding-a-connector-v7-0#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![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/config_up_local_resources.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=M1kICcTl%2BQZxBCGTfdo%2BOlMHJ3FrgfUe%2FHyzz03Qti8%3D) #### 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.clientName` matches 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 `connectorSubnets` are present. #### Protected resources If ***Source NAT from Local Resources*** is disabled: - Traffic appears to originate from the local resource IP - The `ag.connectedSubnets` claim reflects the local resource IP - Ensure return routes exist on protected hosts ![User claims section displaying connector subnets with specific IP addresses listed.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag54-connectedsubnets.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=NJthn5m8ddHMIl5Yyz7p3WnHcGzRL5PP5ZDj6rEaflI%3D) 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. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/alternative_use_case.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=mXfJSuue%2F%2FK9wqMBG615%2B4kFVJAJl9HAif4NYDTLzyY%3D) #### Down rule flow (read from bottom) 1. Protected hosts send traffic to local resource IPs or Connector tun IPs. 2. Gateway VPN processes forward traffic to the Connector client. 3. Connector routes traffic to the local resource using NAT configuration. 4. Local resources return traffic to the Connector. ### Configuring Down access ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/config_down_access_final.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=TqqqcoVNbnUe9jvE1GV8%2BhZiLymU6AnrV1zR%2FdTWrWg%3D) #### Connector configuration 1. Enable the [Connector function](/v1/docs/functions-v7-0#connector) on the appliance. 2. Select the Site to associate with the Connector. 3. 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. 4. If deploying an HA configuration, assign a VIP under [High Availability Configuration](/v1/docs/adding-a-connector-v7-0#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](/v1/docs/ip-pools-v7-0) 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 `connectorSubnets` are 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 ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/down_access_protected_resources.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A58Z&se=2026-11-21T22%3A39%3A58Z&sr=b&sp=r&sig=8ENDJCZBMWZLcE8SeRLRz60z1Cjj6vm7q9uDXeCqvXE%3D) > [!NOTE] > **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](/v1/docs/ssh-command-line-v7-0) for details.