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

Checkpoint firewall common commands part 2

Checkpoint firewall common commands part 2 For basic firewall informaton gathering: fgate stat -Status and statistics of Flood-Gate-1. fwaccel <stat|stats|conns>  – View status, statistics or connection table of SecureXL. fw getifs -Show list of configured interfaces with IP and netmask. cpstat <app_flag> [-f flavour] -View OS, HW and CP application status. Issue cpstat without any options to see all possible application flags <app_flag> and corresponding flavours. Examples: cpstat fw -f policy – verbose policy info cpstat os -f cpu – CPU utilization statistics cpinfo -y all   -List all installed patches and hotfixes. cpd_sched_config print -Show task scheduled with CPD scheduler. enabled_blades -View enabled software blades avsu_client [-app <app>]   , get_version <app>  -Get signature version and status of content security .Without the -app option “Anti Virus” is used. show co...
Post a Comment
Read more

How to modify SSH/HTTP/Telnet time out in Cisco ASA firewall?

How to modify SSH/HTTP/Telnet time out in Cisco ASA firewall? By default tcp idle timeout is 1:0:0 hh:mm:ss. If in case you need to modify it you can do it by MPF (Modular Policy Framework). Let us setup a custom timeout when traffic is coming from particular host 10.77.241.129. !— Match the traffic using the access-list —! object-group service DM_INLINE_TCP_1 tcp port-object eq www port-object eq ssh port-object eq telnet access-list outside_mpc extended permit tcp host 10.77.241.129 <source ip> any object-group DM_INLINE_TCP_1 !— Define the class map Cisco-class –! class-map Cisco-class match access-list outside_mpc !— Call this class-map into policy map and set the connection reset after 10 min when traffic is coming from particular host —! policy-map Cisco-policy class Cisco-class set connection timeout idle 0:10:00 reset !— Apply the policy-map Cisco-policy on the interface. —! service-policy Cisco-p...
Post a Comment
Read more

Unable to Connect to Server Checkpoint R80

Unable to Connect to Server Checkpoint R80 Unable to Connect to Server A connection to the management server will fail if: A firewall between SmartConsole and the management server blocks Port 19009 -  port 19009 is used for a new R80 service. Allow traffic on this port for all clients and management servers. No GUI clients are assigned -  Open the Gaia Portal. If the First Time Configuration Wizard opens, complete it. If the First Time Configuration Wizard has already run, open  User Management > GUI Clients  and add a client. When using Multi-Domain Security Management, connect SmartConsole to the Multi-Domain Server and make sure the domains have GUI clients assigned to them. The required processes are not reachable -  Make sure the computer with SmartConsole installed can reach the IP address of the management server, and that these server processes are up and running: cpm fwm Operation time out  – Your connection ...
Post a Comment
Read more