Static Public IP at Gateway

Static public IP at the gateway involves mapping a static public IP address in the cloud to a device with a private IP address on the LAN. The firewall must have NAT or PAT enabled in order for the device to be protected while still being reachable from the internet. The following image shows a static public IP at gateway configuration with NATing. Double NATing is used to secure the network; the firewall does the first NATing, and the gateway does the second NATing.

However, double NATing is no longer necessary, and the previous firewall can be removed if a customer decides to activate the Adaptiv stateful firewall on the Edge device and the PBX uses a DHCP reservation from Adaptiv Networks' private address space. SASE is advantageous from a security perspective. Similar to traffic optimization within a traditional SD-WAN setup, SASE is focused on security features within a gateway. These features can include web filtering, malware detection, and more.

This image shows public IP address with SASE. Using SASE implies removing the firewall and leveraging the security infrastructure in Adaptiv Cloud. As a result, NATing is done only once, and the need for double NATing is eliminated (double NATing occurs when utilizing a public IP address at gateway with a firewall.) Thus, static IP at gateway with SASE can be beneficial with applications that are sensitive to double NATing, such as VoIP services.

One of the key features included in this configuration include mapping of a static public IP address in the cloud to a device with a private IP address on LAN. This configuration requires NAT masquerading or PAT by the firewall for another private IP in the same subnet of the device LAN, except when using SASE. The traffic is routable from the internet but not directly. This configuration is available for My Connect for remote access. The traffic can be linked to specific gateway (PoP).

In the table below are some sample use cases and benefits of a Static Public IP at Gateway.

Use Case	Explanation
Web Hosting Service	A web hosting provider assigns each client a static public IP address mapped to their private IPs within the cloud. This setup allows clients’ web servers to be accessible from the internet for hosting websites. The cloud firewall performs NAT to maintain security, ensuring web servers are protected while still publicly accessible.
Multi-Site Corporation	A corporation with multiple office locations uses a UCaaS (Unified Communications as a Service) platform to integrate voice, video, and messaging services. Each site has a private IP address for internal devices, with a static public IP address in the cloud mapped to their private IPs. This setup allows the corporation's main server to be accessible from any location via NAT. Remote employees can access the UCaaS platform using My Connect, ensuring seamless communication without direct exposure to the internet. This method balances accessibility with security, suitable for a business with distributed teams.

Use Case

Explanation

Web Hosting Service

A web hosting provider assigns each client a static public IP address mapped to their private IPs within the cloud. This setup allows clients’ web servers to be accessible from the internet for hosting websites. The cloud firewall performs NAT to maintain security, ensuring web servers are protected while still publicly accessible.

Multi-Site Corporation

A corporation with multiple office locations uses a UCaaS (Unified Communications as a Service) platform to integrate voice, video, and messaging services. Each site has a private IP address for internal devices, with a static public IP address in the cloud mapped to their private IPs. This setup allows the corporation's main server to be accessible from any location via NAT. Remote employees can access the UCaaS platform using My Connect, ensuring seamless communication without direct exposure to the internet. This method balances accessibility with security, suitable for a business with distributed teams.