> Source: [sk184327](https://support.checkpoint.com/results/sk/sk184327)

# sk184327 - tcpdump and debug commands show no output when run with g_all or g_alls

| Property | Value |
|----------|-------|
| Solution ID | sk184327 |
| Date Created | 2025-11-17 |
| Last Modified | 2025-11-18 |
| Technical Level | Advanced |
| Products | Scalable Platforms |
| Versions | R82, R81.20, R81.10 (EOS) |
| OS | Gaia |

## Symptoms

- * When running `tcpdump` with `g_all` or `g_alls`, no packets or logs are captured or displayed.

  Note: Running the equivalent command as `g_<command>` works as expected.
* When running debug commands with `g_all` or `g_alls`, the process stops abruptly.

## Cause

The `g_all` and `g_alls` commands run the specified command sequentially on each Security Group Member (SGM). The next SGM is processed only after the command fully completes on the previous SGM.

Tools such as `tcpdump` and many debug commands run continuously until manually stopped, meaning they never complete on the first SGM. As a result, `g_all` / `g_alls` do not proceed to the remaining SGMs.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content