Git Pack Housekeeping: What 34 Minutes of Silence Actually Cost

In Diagnosing a Slow git clone Over SSH With Packet Timing I binned a packet capture into per-minute byte counts and found a 48-minute SSH session that was really 34 minutes of near-silence followed by ~13 minutes of bulk transfer. That post stopped at the diagnosis: the server was building the pack, the network was …

FortiGate – Identifying Non-Offloaded Sessions per Host

In FortiGate - High CPU and Memory load the root cause traced back to sessions that never get hardware-offloaded to the NPU/SPU — DNS and ICMP being the two protocols of interest, since they never leave the CPU path regardless of volume. This note is the workflow for actually finding which host is generating that non-offloaded load, and where it's …

FortiGate – High CPU and Memory load

Recently, we encountered significant CPU and memory utilization spikes on one of our Fortigate Firewalls. Despite consistently handling around 1.5 million sessions for several months without any problems, the situation took a turn for the worse. The firewall became unresponsive through the Command Line Interface (CLI), and at that time, we hadn't configured a dedicated …

Tcpdump examples

Basic Packet Capture tcpdump -i eth0 This captures and displays packets on interface eth0. Capture Packets from a Specific Port tcpdump -i eth0 port 80 This captures packets on port 80 (HTTP traffic) on eth0. Capture Packets with a Specific Host as Source or Destination tcpdump -i eth0 host 192.168.1.100 This captures packets either from …