debug-firewall

Inspect awf-squid and awf-agent containers, Squid logs, and iptables rules to diagnose AWF firewall issues.

123|45|Updated Oct 16, 2025
One-click install
npx skills add https://github.com/github/gh-aw-firewall --skill debug-firewall-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-firewall
Source: https://github.com/github/gh-aw-firewall/tree/main/.claude/skills/debug-firewall
Command: npx skills add https://github.com/github/gh-aw-firewall --skill debug-firewall-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug AWF firewall issues by inspecting containers, traffic logs, and firewall rules to identify misconfigurations or blocked domains.

Core Features & Use Cases

  • Inspect Docker containers awf-squid and awf-agent to verify uptime and status.
  • Analyze Squid access logs to identify denied traffic, malformed requests, or unexpected blocks.
  • Validate iptables rules and network configuration to pinpoint firewall rule issues and connectivity problems.
  • Use-case: during incidents where an agent cannot reach the internet or a domain is incorrectly blocked.

Quick Start

Run a debug workflow against the AWF deployment to surface container health, log insights, and rule statuses.

Frequently Asked Questions about debug-firewall

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

FAQPage Schema
How do I debug AWF firewall issues when traffic is unexpectedly blocked?

Debug AWF firewall issues by inspecting awf-squid and awf-agent container status, reviewing Squid access logs for denied traffic, and validating iptables rules to identify misconfigurations or blocked domains.

What causes DNS and network paths to appear misconfigured in Docker containers?

DNS and network paths appear misconfigured when awf-squid or awf-agent containers report faults, requiring Docker container inspection, Squid log analysis, and host network visibility to verify status and rule sets.

How to check iptables rules and Squid logs for denied traffic in AWF deployments?

Check iptables rules and Squid logs by running a debug workflow against the AWF deployment to surface container health, log insights showing denied traffic or malformed requests, and firewall rule statuses.

Do I need Docker access to diagnose AWF firewall issues across containers?

Yes, diagnosing AWF firewall issues requires access to Docker, container inspection commands, Squid logs, and host or network visibility to verify container status, logs, and iptables rule sets.

Why does an awf-agent container fail to reach the internet during a firewall incident?

An awf-agent container fails to reach the internet when iptables rules or network configuration block traffic, which can be identified by inspecting container uptime, analyzing Squid access logs, and validating firewall rules.