Skip to main content

Checkpoint – Proxy ARP for manual NAT on VSX

Checkpoint – Proxy ARP for manual NAT on VSX



Checkpoint  Checkpoint – Proxy ARP for manual NAT on VSX




In my post Checkpoint – Automatic NAT vs Manual NAT I explained both types of NAT clarifying that the Manual NAT makes neccesary the Proxy ARP entry configuration. This example is for a Checkpoint VSX cluster scenario.
This is an example that was used:
Checkpoint host general properties
Checkpoint NAT rule
The IP that should be configured to answer to ARP request is the 80.80.100.100 (No server in my environment has this IP configured but the Proxy ARP entry will allow the firewall to manage and NAT the packets sent to that IP).
The entry "links" the IP address with the MAC address of the interface that should manage the packet. There is a file that contains all that entrys: $FWDIR/conf/local.arp
So, we have to:
  1. Configure the Policy Global Properties to make this work (only once)
  2. Log in expert mode and edit the $FWDIR/conf/local.arp (if it does not exist, create it) for all cluster nodes.
  3. Install the corresponding policy

Configure the Policy Global Properties

When "Merge manual proxy ARP configuration" is unchecked the local.arp file is ignored.
So ensure this option is checked:
Checkpoint - Merge manual proxy ARP configuration

Add the entry to the local.arp file

Change to the virtual system where the NAT is performed (this is for my perimetral FW – VS1):
[Expert@vsx1:0]# vsenv 1
Context is set to Virtual Device VSX1_EXTERNAL (ID 1).
This is my way to know the MAC address. Surely there are more (and or better) ways:
[Expert@vsx1:1]# ifconfig | grep 80.80.100 -B 1
wrp65       Link encap:Ethernet  HWaddr 00:22:F1:21:C0:0B
            inet addr:80.80.100.10  Bcast:80.80.100.255  Mask:255.255.255.0
Add the entry to the file:
[Expert@vsx1:1]# echo "80.80.100.100 00:22:f1:21:c0:0b" >> $FWDIR/conf/local.arp
[Expert@vsx1:1]# cat $FWDIR/conf/local.arp
80.80.100.100 00:22:f1:21:c0:0b
Be careful when adding the entry on all nodes:
Each of them have its own MAC address. Dont copy&paste the same line on all the local.arp files.

Install the corresponding policy

Install the policy of the affected virtual system:
Checkpoint – Proxy ARP for manual NAT on VSX_1

Other scenarios

Be aware that this configuration is valid for virtual systems on a VSX cluster environment.
Check this official SK30197 for more scenarios.
Labels:

Comments

Post a Comment

Popular posts from this blog

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...
Post a Comment
Read more

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with  SASE (Secure Access Service Edge)  – the convergence of networking and security into one cloud service. Here’s why. 1990s – 2000s: MPLS and the Era of Clear Network Boundaries? Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations. MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is ...
Post a Comment
Read more

FortiGate: Upgrading the firmware via CLI

FortiGate: Upgrading the firmware via CLI To use the following procedure, you must have a TFTP or FTP server that FortiDB can connect to. You must also log in using the “admin” administrator account. Start the FTP or TFTP server. Copy the new firmware image file to the FTP or TFTP server. Log into the CLI. Verify that FortiDB can connect to the FTP or TFTP server. For example, if the IP address of the TFTP server is 192.168.1.168, enter the CLI command: execute ping 192.168.1.168 Enter the following command to copy the firmware image from the TFTP server to FortiDB: execute restore image ftp execute restore image tftp Where is the name and location of the firmware image file and or is the IP address of the FTP or TFTP server. For example, if the firmware image file name is image.out and the IP address of the FTP or TFTP server is 192.168.1.168, enter: execute restore image tftp image.out 192.168.1.168 FortiDB responds with the message: This oper...
Post a Comment
Read more