useful debug command in checkpoint

[Achilles_Tagg]

Please share useful debug command in checkpoint cli if any.

[G_W_Albrecht]

Debug command for which blade ?

[G_W_Albrecht]

sk37030: Debugging Full Synchronization in ClusterXL

sk99008: How to debug and collect VRRP traces in Gaia OS

sk92598: How to debug PIM and Multicast on Gaia

sk84520: How to debug OSPF and RouteD daemon on Gaia

sk101399: How to debug BGP and RouteD daemon on Gaia

[G_W_Albrecht]

sk63560: How to run complete VPN debug on Security Gateway to troubleshoot VPN issues?

sk33327 - How to generate a valid VPN debug, IKE debug and FW Monitor?

sk89940: How to debug VPND daemon 

skI4326 - Enabling IKE and VPN debugging

sk34467: Debugging Site-to-Site VPN

[G_W_Albrecht]

sk98799: Kernel Debug

sk97443: Support Debug Tools

sk103212: Traffic analysis using the 'CPMonitor' tool

sk101878: CPView Utility

sk85780: How to use the 'connstat' utility

[G_W_Albrecht]

sk120260: MTA Debugging and Performance Troubleshooting Toolkit

sk115557: R80.x Security Management server main processes debugging

sk60387: Troubleshooting and debugging Data Loss Prevention (DLP)

sk86320: How to debug CPD daemon

sk86186: How to debug FWM daemon

sk86321: How to debug FWD daemon

[G_W_Albrecht]

And do not forget that fw ctl zdebug - this is wrong...

[jordi_Torres_Ba]

thanks for your time and help

[Timothy_Hall]

How can this epic CheckMates thread not be included:

My Top 3 Check Point CLI commands

--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com

[HeikoAnkenbrand · Accepted solution]

"fw ctl zdebug" is a powertool that is not exhausted from being used with "fw ctl zdebug drop". There is not much to be found in Check Point KB or in the documentation. "fw ctl zdebug" is an R&D tool for testing software in development. Therefore, the insert should be used with care. It starts a debugging in the background until it is aborted with CTRL+C. On productive systems it can have a high performance impact. Furthermore, the debug buffer is not the largest.

fw ctl zdebug" Helpful Command Combinations

fw ctl zdebug + packet
fw ctl zdebug + packet | grep -B 1 TCP |grep -B 1 "(SYN)"      <<< change SYN-ACK,ACK,FIN,... and/or UDP,TCP...
fw ctl zdebug + all |grep -A 1 "Monitor" | grep "1.1.1.1"            <<< change IP address
fw ctl zdebug + all |grep -A 2 "Monitor"
fw ctl zdebug + sync                     
fw ctl zdebug + conn |grep "After  VM:" |grep "(SYN)"
fw ctl zdebug + xlate
fw ctl zdebug + monitorall                                                     <<< use with host IP "| grep 1.1.1.1" or network range "| grep 1.1."
fw ctl zdebug + monitor                                                            <<< use with host IP "| grep 1.1.1.1" or network range "| grep 1.1."
fw ctl zdebug + filter conn | grep -A 8 "rule 1"                          <<< change rule number - show connetions to rule xyz
fw ctl zdebug + filter monitor  | grep -A 8 "rule 2"                     <<< change rule number - show connetions to rule xyz

    
Attention, if you turn on debugging, this will affect the performance of the firewall.

A list with kernel debug flags can be found here:

Kernel Debug Flags R80.10

Kernel Debug Flags R77

[Matlu]

Hello, @HeikoAnkenbrand 

Is there a “debug” command for scenarios where you cannot view logs in real time with SmartConsole?

I need to “know” why a particular traffic is passing through the CLI, as I am now limited to viewing the logs in SmartConsole.

Source: 10.20.100.10
Destination: google.com

I already have a rule created, but I want to “capture” the traffic when the source tries to access google.com from the CLI, to know if the traffic exactly “MATCHES” the defined rule.

Is this possible?

Cheers