Allow public IPv4 access (1:1 NAT)

Quake AI concept: NAT

• Linode exposes this as a per-VPC-interface option called Allow public IPv4 access (1:1 NAT), not as a standalone managed NAT gateway resource. The documentation places it under Edit VPC interface, so NAT is an attribute of the Linode’s interface rather than a separate Neutron-style router or NAT service. Manage Linode interfaces
• The docs describe the behavior as enabling or disabling internet access for the Linode, rather than translating traffic through a separately addressable NAT appliance. If the option is unchecked, the doc says the Linode will not be able to access the internet from that VPC interface. Manage Linode interfaces
• Linode’s VPC model uses a VPC IPv4 address assigned from the subnet CIDR, and the same interface can optionally also get a public IPv4 address. That is different from OpenStack’s common pattern of separate private network ports plus floating IP association, because Linode documents the public access toggle on the interface itself. Manage IP addresses on a Linode
• The networking docs do not describe an API resource for NAT, NAT pools, or router configuration, and the only management steps shown are editing the VPC interface in Cloud Manager and saving the change. The closest documented programmatic surface in the API summary is VPC and interface management, not a distinct NAT endpoint. Linode API summary