---
title: "Enabling a Gateway after configuring the first Controller."
slug: "enabling-a-gateway-v6-7"
description: "Learn how to configure your Controller appliance as a Gateway, enabling secure tunneling and efficient routing for your network."
updated: 2026-03-13T13:47:55Z
published: 2026-04-03T16:41:06Z
canonical: "support.appgate.com/enabling-a-gateway-v6-7"
---

> ## 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.

# Enabling a Gateway

Once you have set up your Controller, the same appliance can also be used as a Gateway. This page details the steps for adding Gateway functionality to the initial Controller. If you wish to add a new appliance to your Collective to be configured as a Gateway, refer to the [Defining a new appliance](/v1/docs/managing-appliance-defining-a-new-appliance-v6-7) section.

## How to configure the Controller appliance to also be a Gateway

### Configure the default Site or add a new Site

The pre-defined default Site uses entitlement-based routing (EBR) to set the client routing and has no name resolution (DNS) set, so the appliance's DNS setting will be used. This default Site can often be used as is. However, before adding the Gateway functionality, you may want to edit the default Site. The default Site defines the group of Gateways used to protect specific hosts/networks.

To edit the Site:

1. Go to the **Sites** page (System > Sites).
2. Select the default Site to open the **Edit Site** page.

For more information, see the [Sites](/v1/docs/sites-v6-7) page.

> [!NOTE]
> **NOTE**
> 
> If you want to create a new Site you will have to get an [additional license](/v1/docs/licenses-v6-7).

![A screenshot of the Editing Site page.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag55-sites.png?sv=2026-02-06&spr=https&st=2026-10-26T23%3A24%3A52Z&se=2026-10-27T00%3A24%3A52Z&sr=c&sp=r&sig=2%2FbB91Lw%2Fvbf%2FOaDR%2B7%2FAuiXjaXlK%2BsCgTZY0R6LwNY%3D)

### Change the appliance functionality

To configure your Controller to function as a Gateway:

1. In [Appliances](/v1/docs/functions-v6-7) (System > Appliances), click on the name of your Controller appliance.
2. In the **Edit Appliance** page, go to the **Functions** tab and select *Gateway* under ***Appliance Functions***.
3. In the ***Appliance Site*** dropdown, select *Default Site* or the site you configured for the appliance.
4. In ***Secure Tunnel Settings***, select **+Add** to add an address to *Client Tunneling - Allowed Destinations*. If this is left blank, no traffic will be allowed out of the secure tunnel.

Once you have entered the configuration setting, press select **Save** and the new settings should be applied immediately.

### Check the result

On the **Appliances** page, your Gateway should be noted as enabled and with a status of *Healthy*.

![Overview of appliances health status, highlighting warning and healthy statuses for various components.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag61-dash_appliances_warning.png?sv=2026-02-06&spr=https&st=2026-10-26T23%3A24%3A52Z&se=2026-10-27T00%3A24%3A52Z&sr=c&sp=r&sig=2%2FbB91Lw%2Fvbf%2FOaDR%2B7%2FAuiXjaXlK%2BsCgTZY0R6LwNY%3D)

If you want to add more functionality to your new appliance, select the Appliance and go to the **Functions** tab to enable another function. Click **Save** and you will see your function enabled and the appliance status as Healthy. When adding more functions ensure there is sufficient [RAM and disk space available](/v1/docs/instance-sizing-v6-7).