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

# sk181640 - TCPdump shows no output when filtering with "any" interface

| Property | Value |
|----------|-------|
| Solution ID | sk181640 |
| Date Created | 2023-11-09 |
| Last Modified | 2023-11-12 |
| Technical Level | Advanced |
| Products | Other |
| Versions | Not Version-Specific |
| OS | Gaia |

## Symptoms

- * In some scenarios, when running tcpdump with a filter to "any" interface, the output shows no traffic.
* When removing the Health Probe configuration from the *fwkern.conf* file, the traffic is captured.

## Cause

Some traffic types go directly to a specific interface's queue, while avoiding any socket tcpdump listens to. This causes tcpdump to not catch this traffic.

## 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