> Source: [sk172625](https://support.checkpoint.com/results/sk/sk172625)

# sk172625 - Traffic arriving from the Internet on Azure HA does not get accelerated

| Property | Value |
|----------|-------|
| Solution ID | sk172625 |
| Date Created | 2021-04-19 |
| Last Modified | 2026-05-10 |
| Technical Level | General |
| Products | Cloud Firewall |
| Versions | R81 (EOS), R81.10 (EOS), R81.20, R82 |
| OS | Gaia |
| Platform | Azure |

## Symptoms

- Traffic arriving from the Internet on Azure HA does not get accelerated

## Cause

As part of Check Point architecture on Azure, incoming traffic from the internet is configured to be NATed on the External Load Balancer. Following this NAT, the ELB sends the packet with the Check Point Gateway as the destination.   
As part of SecureXL architecture, any packet that arrives with the gateway's IP as destination is processed as F2F and is not accelerated.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 62
* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 622

<br />

<br />

If you choose not to upgrade, enable the Floating IP option on Azure. This sends the traffic to the Check Point Gateway with the original destination IP of the packet.

<br />

**To configure a Floating IP:**   

1. Log into Azure portal and navigate to the Resource Group where the frontend Load Balancer resides.  

2. Click on the frontend Load Balancer object (named frontend-lb). From the left menu select Load Balancing Rules.  

3. Enter the relevant Load Balancing Rules based on the [Cloud Firewall for Azure High Availability Cluster Deployment Guide.](https://sc1.checkpoint.com/documents/IaaS/WebAdminGuides/EN/CP_CloudGuard_Network_for_Azure_HA_Cluster/Content/Topics-Azure-HA/Workflow.htm)  

4. Go to SmartConsole and configure the NAT rules according to the Deployment Guide. Make sure to follow the note that recommends setting the Original Destination to be the External Load Balancer Frontend IP Address.  

Example:  

Original Source: Any  
Original destination: \<Destination_IP\> (i.e. Public IP of the server)  
Original Service: \<NATed_port\> (i.e. 8083)  
Translated Source: Original  
Translated Destination: \<Destination_Internal_IP\> (i.e. Internal IP of the server)  
Translated Service: \<Port_before_NAT\> (i.e 80)  

<br />

5. To have the changes take effect, install policy to the Security Gateway.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
