Most of us already live inside our IDEs. But when a network issue hits, we still bounce between terminals, browser lookups, config files, SSH tools, screenshots and notes and don't forget context switching is where mis
takes happen specially when we have dozens of windows opened.
So I built Net Commander aimed to be an open network engineering toolkit built inside VS Code, designed to keep troubleshooting data-driven and consistent.
What it includes today:
- Ping + traceroute, supercharged (single host, multiple targets or entire CIDRs for convenience)
- Lookups: IANA ports, ASN/public IP info, PeeringDB
- Calculators: RFC-compliant CIDR + “what-if” subnet simulation
- Wi-Fi quick surveys + capture workflows (for wireshark deeper analysis later)
- SSH profiles for fast host jumps
- Network config colorizer with inline detection including useful tooltips for private/public IPs
- Root Cause Analysis checklist ready to use with platform-specific commands (Cisco, Arista, Ciena, Azure, AWS, GCP)
I’d love your feedback:
- Which workflow would save you the most time inside VS Code?
- What tool should I add or integrate next?
Top comments (0)