network-diagnosis

To diagnose intermittent packet loss and latency spikes on a Linux server, the network-diagnosis skill automatically collects system snapshots across L1-L4 layers, correlating interface statistics and kernel logs to identify root causes. It provides non-destructive, evidence-based remediation suggestions.

The best way to perform multi-layer network troubleshooting across L1 to L4 layers is to capture comprehensive system state data, including ARP table health, IP conflict detection, and MTU path verification, correlating these snapshots with routing tables and firewall rules for standardized reporting.

You can automatically collect network diagnostic snapshots for connectivity failures by running the network-diagnosis skill, which captures interface statistics, routing tables, and firewall rules within a specific time window to provide an evidence-based root cause analysis.

Linux network fault diagnosis does not require manual intervention to identify root causes when using this automated framework, which systematically evaluates interface statistics and kernel logs to generate a prioritized list of potential issues and non-destructive remediation suggestions.

Yes, you can analyze eth0 connectivity issues for the last 30 minutes by invoking the skill to collect and correlate diagnostic snapshots within that specific time window, matching interface statistics against system logs to isolate the fault.

To perform automated network fault analysis in Linux environments, the required dependencies include bash, iproute2, ethtool, and arping, which collectively enable systematic snapshot collection and multi-layer evaluation of interface and routing health.