Openclaw Network Diagnostics

Standalone advanced network diagnostics for OpenClaw to continuously test end-to-end connectivity from OpenClaw agent to Telegram Bot API and approximate del...

This package appears to do what it says, but take these precautions before deploying: (1) Review the full scripts/netdiag.py source yourself (or have someone you trust) to confirm there are no unexpected network endpoints or hidden behaviors. (2) Keep your Telegram bot token and personal chat id out of world-readable locations; prefer a restricted config file and OS-level secret storage. (3) Ensure logging.redact_sensitive_fields is true before running; if you must share logs externally (AI analysis, etc.), mask tokens and PII first. (4) Run the worker as an external background process (the SKILL.md recommendation) rather than in-process to avoid impacting OpenClaw runtime. (5) Start in a sandboxed host or staging environment to observe actual network traffic and any subprocess invocation (ping/traceroute/dig) before deploying to production. (6) If you supply a proxy_url or NETDIAG_CONFIG via environment, double-check those values to prevent accidental routing of telemetry to an unintended server.

Type: OpenClaw Skill Name: openclaw-network-diagnostics Version: 0.1.1 The skill bundle provides a network diagnostic tool that executes system commands (ping, traceroute, dig) via subprocess using parameters from a configuration file (scripts/netdiag.py). While these functions support the stated purpose of monitoring Telegram Bot API connectivity, the lack of strict sanitization on configuration values like 'telegram_api_host' could allow for argument injection attacks. Furthermore, the tool's ability to run as a persistent background process and its handling of sensitive Bot Tokens, combined with instructions to upload detailed telemetry logs to external AI services (references/ai-log-analysis.md), creates a high-risk profile for data exposure and system abuse.