netfilter-conntrack-diagnosis

Diagnose Linux Netfilter, iptables, nftables, and conntrack connectivity issues by correlating rule chains with connection states.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill netfilter-conntrack-diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netfilter-conntrack-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/netfilter-conntrack-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill netfilter-conntrack-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves complex network connectivity issues caused by Linux Netfilter, iptables, nftables, and conntrack misconfigurations or resource exhaustion, which are often invisible to standard network tools.

Core Features & Use Cases

  • Parallel Analysis: Simultaneously audits rule chains and connection tracking states to identify discrepancies.
  • Root Cause Isolation: Pinpoints specific failure points like nf_conntrack table overflows, NAT mapping errors, or stateful rule drops.
  • Use Case: When a production service experiences intermittent connection resets or packet loss, use this Skill to determine if the issue is due to conntrack table saturation or an incorrectly ordered firewall rule.

Quick Start

Run the netfilter-conntrack-diagnosis skill to collect baseline data and analyze the current firewall and connection tracking state on this host.

Frequently Asked Questions about netfilter-conntrack-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Linux conntrack table exhaustion in high-concurrency environments?

You diagnose conntrack table exhaustion in high-concurrency environments by auditing connection tracking states against rule chains to identify nf_conntrack overflows causing intermittent connection resets.

Why does my Linux server experience intermittent connection resets when firewall rules look correct?

Intermittent connection resets happen when firewall rules are correct but conntrack table saturation drops packets. This Skill audits rule chain traversal and connection tracking states to isolate stateful rule drops.

What is the best way to troubleshoot NAT mapping failures in iptables or nftables?

Troubleshooting NAT mapping failures in iptables or nftables requires parallel analysis of rule chain traversal and connection tracking states to pinpoint translation errors and stateful rule drops.

How can I get kernel-level visibility into iptables rule hits and packet drops?

Gain kernel-level visibility into iptables rule hits and packet drops by running this Skill to collect baseline data and audit firewall rule chains against current connection tracking states for discrepancies.

Does this Skill diagnose both nftables and legacy iptables connectivity issues?

Yes, it diagnoses both nftables and legacy iptables connectivity issues by deep-diving into Linux kernel Netfilter to correlate rule chain traversal with connection tracking states for NAT and firewall failures.