Exit nodes
Route internet traffic through a private gateway or Orbit.
An exit node carries a device’s internet-bound traffic. It can be one of your own gateways with Exit Node enabled, or a Pulse Orbit public point of presence. Egress policies, on the Egress Policies tab under Network → Access, decide whether a scope must, may or may not use an exit and which exits it may pick.
Before you start#
- Changing a gateway’s exit flag needs
gateways:update. Egress policies needpolicies:createto add,policies:updateto edit or reorder andpolicies:deleteto remove. - For a private exit, the gateway host must be able to masquerade. The gateway drawer shows Egress broken when the masquerade interfaces are missing; exit traffic through that gateway is dropped until fixed.
- For Orbit, the tenant must have Orbit enabled with at least one opted-in region. See Orbit.
- With no egress policy at all, every device gets the default: exit Optional with Auto selection.
Enable a private exit#
- Open Network → Gateways, choose Edit gateway and turn on Exit Node. Click Save Changes.
- Back in the list, the Exit column shows Active. In the drawer, Exit Node reads Enabled.
- Create or edit an egress policy (below) so devices are allowed or required to use it.

The Exit Node switch on the edit form is the only step needed to make a private gateway available as an exit.
Create an egress policy#
- Open Network → Access, switch to Egress Policies and click Add Egress Policy.
- Under Scope choose Entire Tenant, Specific Role, Specific Group or Specific Device. For anything but the tenant, enter the Role ID, Group ID or Device ID. Saving without one shows Please enter a subject ID for the selected scope.
- Under Routing Mode choose Required (traffic must use an exit; fails closed if none is available), Optional (users may enable an exit) or Disallowed (no exit for this scope).
- Under Constraints (hidden for Disallowed) set Selection Strategy to Auto or Pinned, choose Public path (Orbit) (Auto (default), Prefer private, Prefer Orbit or Orbit only), and optionally restrict Allowed Regions, Specific Gateways and Pulse Orbit Regions. Empty lists mean no restriction.
- Set Priority (lower wins among policies with the same mode) and click Create Policy.
One policy exists per scope. Editing the tenant policy, or a role, group or device policy, reopens the same row. Delete Policy removes it.

Scope and routing mode come first; the Constraints section appears for Required and Optional and hides for Disallowed.
How the winning policy is chosen#
For each device the control plane collects the policies for the device, its groups, its roles and the tenant, then picks one:
- The more restrictive Mode wins regardless of priority: Required beats Disallowed, which beats Optional.
- Among policies with the same mode, the lower Priority number wins.
The winning policy then filters exit gateways. Disallowed allows none. Auto with no regions or gateways listed allows every exit-enabled gateway. Otherwise a gateway passes when it is in Specific Gateways or its region is in Allowed Regions. The same filter runs on the gateway side, so a device cannot use an exit its policy forbids.
For Orbit, the control plane expands the tenant’s opted-in regions to live PoPs and intersects them with the policy’s Pulse Orbit Regions. If nothing survives, Orbit is off for that device and a Prefer Orbit or Orbit only preference is downgraded to Prefer private.
Read the list#
| Column | Meaning |
|---|---|
| Scope | Entire Tenant or Role: <id>, Group: <id>, Device: <id> |
| Mode | Required, Optional or Disallowed |
| Selection | Auto or Pinned, with the public path preference underneath when not Auto |
| Gateways | N selected or All |
| Orbit regions | Restricted or All |
| Regions | Allowed gateway regions, or All |
A line above the table reports what Orbit resolves to for the tenant, for example Orbit egress resolves to N PoPs in London (United Kingdom), Pulse Orbit is disabled for this tenant., or a warning that Orbit resolves to no eligible PoPs and agents will stand Orbit down.

One row per scope: the mode chip, the selection strategy with its public path preference, and whether gateways or Orbit regions are limited.
Troubleshooting#
- Traffic still leaves the device directly. Check that the gateway shows Exit: Active, that the winning policy for this device is Required or the user turned the exit on under Optional, and that the gateway passes the policy’s region and gateway filters. Remember a more restrictive mode on another scope overrides priority.
- Devices with “Required” lose internet access. Required fails closed when no allowed exit is available. Check the exit gateways are Online and not Egress broken.
- “No exit-capable gateways found” in the form. No gateway has Exit Node enabled yet.
- Orbit is never used despite “Prefer Orbit”. Orbit is disabled, no region is opted in, or the policy’s Pulse Orbit Regions exclude every opted-in region. Read the summary line above the table and open Orbit settings.
- Saving fails with a message about Orbit region codes. The stored region list contains values the console cannot write back safely. Follow the message: fix the stored value or choose the region selection explicitly.
- A reorder is cancelled. One row’s Orbit regions could not be reproduced exactly, so nothing was written. Edit that policy first.
Egress policy controls general internet routing. It does not replace an access policy for a private service, and it does not by itself enable Secure Web or Firewall rules.