--- title: "Adding a Gateway" slug: "adding-a-gateway-v7-0" description: "Learn how to configure a Gateway in AppGate for secure user access, including TLS settings, load balancing, and client tunneling options." tags: ["Appliance Configuration", "Gateway", "Appliance Functions"] updated: 2026-10-05T18:44:52Z published: 2026-10-05T18:44:52Z canonical: "support.appgate.com/adding-a-gateway-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. # Adding a Gateway A Gateway acts as an enforcement point and controls user access to protected resources. This section describes how to configure a Gateway in an AppGate system. --- ## Before Adding a Gateway Before configuring a Gateway, ensure that client-to-appliance communication is set up correctly: - The *Client hostname/IP* configured under ***Secure Tunnel Settings*** is passed to clients and used to establish the secure tunnel to the Gateway using TLS on port 443. - DTLS can be enabled for tunneled traffic at the [Site](/v1/docs/configuring-sites-v7-0) level. When DTLS is enabled, client-to-Gateway communication for that Site uses UDP port 443. The same client hostname/IP is used. - For high availability (HA) Gateways, it is recommended to use the built-in Gateway load-balancing capability provided by the AppGate ZTNA system. This allows the use of the weighting values defined in ***Secure Tunnel Settings***. - HA Gateways can be fed by independent networks or ISPs, providing full failover without a single point of failure. --- ## Configuring a Gateway To configure a Gateway: 1. In the **Add/Edit Appliance** page, select the ***Gateway*** checkbox in the **Functions** tab. 2. Complete the following configuration fields: ### Site Settings - ***Appliance Site***. Select the Site from the dropdown list. ### System TLS Connection (using SPA) These settings are used for peer‑to‑peer traffic: - ***TLS Port***. The inbound TLS connection port to the appliance. - ***Allowed Sources***. Select **+Add** to add one or more allowed sources by adding the *Address*, *Netmask Length*, and the *Network Interface*. The requesting IP address must match at least one allowed source. - ***SPA Mode***. Allows the SPA mode to be changed for a specific appliance. Select one of the following: - *No override* - *Check TCP SPA key before allowing connections* - *Check UDP (and TCP) SPA key before allowing connections* - ***Enable proxy protocol****.* When enabled, the appliance accepts only packets that include a proxy protocol header. AppGate ZTNA supports proxy protocol versions 1 and 2. > [!NOTE] > NOTE > > When traffic originates from a known source, add that source to *Allowed Sources*. Failure to do so introduces a security risk. ### Secure Tunnel Settings - ***Client Hostname/IP***. Enter a fully-qualified domain name or an IPv4 or IPv6 address. This hostname is used only to inform clients where to find the appliance. > [!NOTE] > NOTE > > Changing the client hostname on an active appliance may cause client connections to fail until the appliance certificate is renewed. > [!NOTE] > NOTE > > To allow clients to create tunnels using IPv4 or IPv6, the Gateway must be configured with a single fully-qualified domain name that has: > > - An IPv4 A record. > - An IPv6 AAAA record in public DNS. - ***Client Tunneling – Load Balance Weighting Factor***. Enter the weighting factor. The default value is 100. This value can be set independently of any external weighting factor. For more information, see the section on [Controller and Gateway HA mechanisms](/v1/docs/high-availability-ha-v7-0#controller-and-gateway-ha-mechanisms). - ***Connect via Local Network***. Select ***Configure***, then enter the *Local Client Hostname/IP* and the *Local Client Tunneling – Load Balance Weighting Factor*. When a client is on the local LAN, it connects using the local client hostname or IP address instead of the external one. - ***Client Tunneling – Allowed Destinations***. Select **+Add** to open the **Target** window. Configure the destination’s *Address (Optional)*, *Netmask Length (Optional)*, and *Network Interface (Required)*. Only the specified destinations are allowed for secure tunnel traffic. - ***Client Tunnel QUIC Port***. The port used for tunneling between the Gateway and the client. The default port is 443. After completing the Gateway configuration, continue to the [**Miscellaneous**](/v1/docs/adding-a-new-appliance-v7-0#miscellaneous) tab.