R80.x Performance Tuning and Debug Tips – TCPDUMP vs. CPPCAP

Document created by Heiko Ankenbrand Champion on Dec 2, 2018Last modified by Heiko Ankenbrand Champion on Dec 3, 2018
Version 10Show Document
  • View in full screen mode
What is CPPCAP?


TCPDUMP is a Linux tool which at times is not suitable for use with Gaia. Running TCPDUMP causes a significant increase in CPU usage and as a result impact the performance of the device. Even while filtering by specific interface or port still high CPU occurs. Check Point created a tool which works better with Gaia OS.

 

Chapter

 

Architecture:

R80.x Security Gateway Architecture (Logical Packet Flow)

R80.x Security Gateway Architecture (Content Inspection) 

R80.x Security Gateway Architecture (Acceleration Card Offloading) 

R80.x Ports Used for Communication by Various Check Point Modules 

Performance Tuning:

R80.x Performance Tuning Tip - AES-NI 

R80.x Performance Tuning Tip - SMT (Hyper Threading) 

R80.x Performance Tuning Tip - Multi Queue 

R80.x Performance Tuning Tip - Connection Table 

R80.x Performance Tuning Tip - fw monitor

R80.x Performance Tuning Tip - TCPDUMP vs. CPPCAP 

R80.x Performance Tuning Tip – DDoS „fw sam“ vs. „fwaccel dos“ 

 

CPPCAP

 

Tip 1 

 

"CPPCAP" is a traffic capture tool which provides the most relevant outputs and is similar to Tcpdump. The tool is adjusted to Gaia operating system yet requires installation of an applicable RPM.

 

The good news! SecureXL can be enabled or disabled to capture with CPPCAP.

 

You can download this tool for R77.30, R80.10 and R80.20. Get more details here: sk141412

 

Instal and use:

  1. Download the RPM package (sk141412) and transfer the RPM package with winscp to appliance or open server.
  2. Install the RPM using the following command:
    # rpm -ivh --force --nodeps <RPM_FILE>
    # /etc/init.d/start_cppcap start
  3. Start cppcap to sniffing packages (for example on interface eth0 with parameter "N"):

    On internal Interface (example "ping 8.8.8.8" from client IP 10.1.2.1 to server IP 8.8.8.8)
    :
    #
    cppcap -i eth0 -N  |grep ICMP

       
        On external Interface:

        # cppcap -i eth2 -N  |grep ICMP

 

Notes:

- To have all verbos information add "-DNT" to the syntax to filter out specific interface or VS by using capital letters.
- It will provide outputs on ARP IPV4/IPV6, TCP and UDP traffic. Dynamic routing information will not show all verbose information.

 

Tip 2

In and out (see red marked point in picture):

In       - Is the incoming packet on the firewall on the inbound interface from the point of view of the first packet. It is simalary to fw monitor inspection point "i" client to server packet.

Out    - Is the outgoing packet on the firewall on the inbound interface from the point of view of the first packet. It is simalary to fw monitor inspection point "O" server to client packet.

 

On the outgoing interface (see blue marked point in picture), the view is exactly inverse.

 

Tip 3

FlagExplanation
 -vV VSID                   lowercase to capture only from specific VSID, uppercase for all exec pt VSID
 -iI DEVICE lowercase to capture only from specific DEVICE, uppercase for all execpt DEVICE         
 -d DIR capture specific direction ('in' for inbound, 'out' for outbound)
 -f "EXPR" filter specific expression, for syntax, see pcap-filter(7)
 -o FILE save capture to a FILE
 -c NUM capture up to NUM bytes of frame (default 96, '0' for any size)
 -p NUM capture NUM frames before stopping
 -b NUM capture NUM bytes before stopping
 -D verbose datalink layer
 -N verbose network layer
 -T verbose transport layer
 -Q omit time from output
42 people found this helpful

Attachments

    Outcomes