net-dhcp-path

Analyze DHCP latency, timeouts, and relay-path behavior across clients, SSIDs, VLANs, or sites.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ekkus93/vscode_skills --skill net-dhcp-path
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: net-dhcp-path
Source: https://github.com/ekkus93/vscode_skills/tree/main/skills/net-dhcp-path
Command: npx skills add https://github.com/ekkus93/vscode_skills --skill net-dhcp-path

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nettools-core.

What problem does it solve?

DHCP health issues, latency problems, and relay-path anomalies across clients and network segments are identified and triaged to speed network restoration.

Core Features & Use Cases

  • Evaluates DHCP offer latency, ACK latency, timeouts, scope pressure, and relay-path correctness using the bundled NETTOOLS contracts.
  • Targets precise contexts via primary selectors (--client-id, --client-mac, --ssid, --vlan-id, --site-id) and optional scope selectors (--ap-id, --ap-name, --switch-id, --switch-port).
  • Outputs a structured SkillResult in JSON with evidence, findings, and recommended next actions.

Quick Start

Run the net_dhcp_path.py script with a target context to generate a diagnostic JSON report.

Frequently Asked Questions about net-dhcp-path

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

FAQPage Schema
How do I diagnose DHCP latency and relay-path anomalies across multiple VLANs?

You can diagnose DHCP relay-path behavior by running the diagnostic script with primary selectors like --client-id, --ssid, or --vlan-id. It evaluates offer latency, ACK latency, and timeouts, returning a structured JSON report with evidence and next actions.

What is the best way to troubleshoot DHCP scope pressure and client timeouts?

Troubleshooting DHCP scope pressure involves analyzing latency metrics and timeouts against network contracts. The tool identifies health issues across clients and segments, returning a JSON SkillResult with detailed evidence and recommended next actions to speed network restoration.

Do I need Python 3 to run DHCP relay-path diagnostics?

Yes, Python 3 is required to run the DHCP relay-path diagnostics. The tool relies on the bundled nettools-core package and requires a Python 3 environment to execute its diagnostic rules and produce the structured JSON output with latency metrics.

Can I target a specific switch port or access point when analyzing DHCP health?

Yes, you can target specific contexts when analyzing DHCP health by using optional scope selectors like --ap-id, --switch-id, and --switch-port alongside primary selectors to narrow the diagnostic results to specific network segments.

Why does DHCP relay-path analysis output a JSON file instead of a text log?

DHCP relay-path analysis outputs a structured JSON SkillResult to provide machine-readable evidence, latency metrics, and recommended next actions. This format allows automated parsing and integration into broader network restoration workflows.

What are the limitations of using bundled network contracts for DHCP diagnostics?

A limitation of using bundled network contracts for DHCP diagnostics is the strict dependency on the nettools-core package. The tool applies precise diagnostic rules to identify issues but requires a Python 3 environment to function.