Bigleaf assigns each customer site a dedicated public IP block that is fully managed and routed through the Bigleaf Cloud Access Network. These IPs are independent of the addresses provided by your ISPs, giving your site a stable, circuit‑agnostic public identity on the internet.
This architecture is the backbone of Bigleaf’s session‑preserving load balancing and failover. Because your public IPs come from Bigleaf—not your ISPs—your IP address never changes, even when traffic shifts between circuits. As Bigleaf’s Intelligent Load‑Balancing system moves sessions across links, all active connections remain uninterrupted:
- VPN tunnels stay up
- VoIP calls continue without drops
- Application sessions persist
- External services always see the same IP
By decoupling your public IP identity from your ISP circuits, Bigleaf ensures consistent reachability, seamless failover, and simplified network design across multi‑WAN environments.
How Bigleaf Public IPs Are Used
Bigleaf supports two deployment configurations, and each one uses the Public IP block differently:
- External Firewall — Integrate your existing firewall into the Bigleaf deployment
- Bigleaf Edge Firewall — Use Bigleaf’s built‑in Edge Firewall service
The sections below explain how the Public IP block behaves in each configuration.
External Firewall
When you’re integrating Bigleaf with an external firewall, the Bigleaf router exposes the Public IP block as a routed LAN network. In this deployment, LAN mode must be set to Static so the firewall can consume the usable Bigleaf‑assigned static IPs directly.
How the IPs are allocated
- Bigleaf reserves three IPs for the gateway, network, and broadcast addresses.
- In HA deployments, Bigleaf reserves two additional IPs (HA device + virtual IP).
- All remaining IPs are available for customer use.
Typical usage
- The external firewall connects to the Bigleaf router’s LAN interface.
- The firewall uses one of the usable Bigleaf public IPs as its WAN address.
- Downstream servers or services can consume additional public IPs directly or via the firewall’s NAT rules.
Example: Your external firewall receives a Bigleaf public IP. Any LAN client behind that firewall—such as a security camera—can use the remaining Bigleaf public IPs by assigning the IP directly or publishing it through the firewall’s NAT rules.
Bigleaf Edge Firewall
When using the Bigleaf Edge built‑in firewall, the router automatically operates in NAT LAN mode. In this configuration, the Public IP block is not exposed as a routed LAN network. Instead, the entire block is available to map to private LAN clients using NAT rules.
How the IPs are allocated
Bigleaf automatically assigns a dedicated public network address that the Edge firewall uses as its NAT source for translating private LAN addresses.
- All IPs in the customer’s Public IP block are fully usable for 1:1 NAT.
- Each usable public IP can be mapped to a private LAN client behind the Bigleaf router.
- The Bigleaf Edge firewall handles all inbound and outbound translation automatically.
Typical usage
- Mapping internal devices—servers, cameras, appliances—to public IPs.
Example: Your Bigleaf Edge firewall is assigned a dedicated public network address for NAT operations. All other IPs in your Public IP block can be used for 1:1 NAT. A LAN client—such as a security camera with a static private IP—can be mapped to one of these public IPs, allowing remote users to reach the device while it remains protected on the private LAN.
See the following article on where to find your IP addresses in the Bigleaf Cloud Connect Dashboard -- How to find your public IP addresses
Comments
0 comments
Article is closed for comments.