Network

Open the gateway → Network tab in my.cubepath.com.

Public addresses

The gateway's public IPv4 and IPv6, with their netmask and rDNS. The IPv4 is the address the internet sees for every server behind the gateway — this is the one you give a third party to whitelist.

Tip

Set the rDNS to something identifiable, like nat-prod.example.com. When a partner asks which of your addresses is calling their API, a meaningful reverse record answers it without a ticket.

Attached private network

The private network the gateway serves, with its CIDR and the gateway's private IP inside it. Every server on this network can reach the internet through the gateway.

The auto-managed route

A default route — 0.0.0.0/0 via the gateway's private IP — is created automatically on the network. It's what actually sends outbound traffic through the gateway, and it appears in the network's route list alongside any routes you've added yourself.

Important

This route is managed for you and can't be deleted directly. Deleting the NAT Gateway removes it.

If you want only some traffic to take the gateway, add your own narrower routes on the network alongside it. A more specific route always wins over the catch-all default, so a route for a particular CIDR pointing somewhere else keeps that traffic off the gateway while everything else still egresses through it.

From here you can jump straight to the network's full route list to see how the two interact.