Checkpoint Notes

-

1. use SCP to transfer file

It is recommended to add a new user with "scponly" shell, instead of changing admin user to "bash" shell





















2. Reset SIC
In case SIC has issue or policy deployment causes connection loss to GW, reset SIC will load initial policy.
on GW:
cpconfig, choose 5, set one time activation key,  then choose 10. 
On SMS:
firewall properties > General Properties > [Communication] 

3. object used in Firewall Policy
If an object has private IP and static NAT. The firewall policy use the object for inbound and outbound rule, no need specify its private or public IP. 

4. Inline Policy
regular rule can only select service (port), after Action uses Inline Layer, the subrule can use application and URL.

5. Backup
 /var/log/CPbackup/backups/
system backup:
   GUI, backup Gaia config.
   CLI: add backup / set backup restore


6. Ping
Global Properties > Accept ICMP requests
implied rule "before last" literally means, before the last explicit rule, which is usually the cleanup policy rule. ICMP "Before Last" is disabled by default.


7. VPN peer ping CP public IP failed.
By default, Check Point gateways will include the public IP of the peer gateway in the encryption domain of the tunnel. This means that when you are behind your gateway, and ping to the public IP address of the gateway on the other end, CP will encrypt these pings and send them through the tunnel. Most likely this does not work because this behavior is not supported by the gateway on the other end. There is a way around this. You can exclude specific IP addresses from the encryption domain by adding them to the $FWDIR/lib/crypt.def file on your management server. Make sure you take a backup of the file before making any permanent changes (in case shit hits the fan). Log into your management server cli, open $FWDIR/lib/crypt.def in a text editor, find the following line "#define NON_VPN_TRAFFIC_RULES 0", replace this line with "#define NON_VPN_TRAFFIC_RULES (src=[IP_addr_of_vpn_peer])" Then save your changes, and install policy to push this file to the relevant gateways. The gateways should now no longer encrypt traffic destined for the public IP of the peer gateway, so your pings should start working again.






Comments

Post a Comment

Popular posts from this blog

Firepower FMC and FTD troubleshooting

-
 1. Display real time log on FMC or FTD: pigtail for example: pigtail | grep 192.168.2.20                      pigtail | grep sftunnel 2. Restart communication channel manage_procs.pl run it from  the sensor only, run it from FMC will reset all sensors' channel. This scripts are nice to be used when the FMC and FTD have communication problems like heartbeats are not received, policy deployment is failing or events are not received > expert ************************************************************** NOTICE - Shell access will be deprecated in future releases          and will be replaced with a separate expert mode CLI. ************************************************************** admin@FTD:~$ sudo su Password: root@FTD:/home/admin# manage_procs.pl ****************  Configuration Utility  **************  1   Reconfigure Correlator  2   Reconfigure and flush Correlator  3    Restart Comm. channel  4   Update routes  5   Reset all routes  6   Validate Network  0   Exit *****
Read more

ASA IKEv1 VPN troubleshooting Steps and Tips

-
  1. Phase I proposal mismatch  Run show crypto isakmp sa  Initiator: MM_WAIT_MSG2 Responder: No info  Most likely this is phase1 proposal mismatch, verify IKEv1 policy, other symptoms:   Initiator log: Information Exchange processing failed All configured IKE versions failed to establish the tunnel Initiator debug: Received an un-encrypted NO_PROPOSAL_CHOSEN notify message, dropping Responder log: Error processing payload: Payload ID Responder debug:  All SA proposals found unacceptable 2. IKE version mismatch:  Run  show crypto isakmp sa  no info at both initiator and responder Initiator log: Removing peer from correlator table failed, no match! Reason: User Requested  All configured IKE versions failed to establish the tunnel Initiator debug: Oakley begin quick mode PHASE 1 COMPLETED IKE Initiator sending 1st QM pkt Removing peer from correlator table failed, no match! Session is being torn down. Reason: User Requested Responder log: Tunnel Rejected: Conflicting protocols specified
Read more

Firepower 2100/1100 FTD/ASA initial setup, reimage, upgrade.

-
  Chassis FXOS and FTD share same management IP (default 192.168.45.45) Chassis FXOS (192.168.45.45) and ASA ()use different management IP although on same physical interface. SSH to FXOS/FTD are on FTD CLI prompt, go to FXOS using the  connect fxos  command Console to Chassis is on FXOS CLI prompt, go to FTD using the  connect ftd  command The Firepower 1100 does not support the FXOS Firepower Chassis Manager; only a limited CLI is supported for troubleshooting purposes. The Firepower 2100 runs an underlying operating system called the Firepower eXtensible Operating System (FXOS).  If you run ASA on Firepower 2100, ASA can be in the following modes: Appliance mode (the default after ASA 9.13)—Appliance mode lets you configure all settings in the ASA. Only advanced troubleshooting commands are available from the FXOS CLI. See the  FXOS troubleshooting guide  for more information. Firepower Chassis Manager is not supported . ciscoasa# connect fxos [admin] Connecting to fxos. Connected
Read more