What SubnetSlinger needs, and removing it

Self-contained by default: the core tools — ping, trace, DNS, ports, SNMP, speed test, subnet calc, HTTP/TLS/WHOIS, discovery, the local servers, the SSH client, the vault — need nothing installed. They run on the bundled runtime.

A few tools call OS commands that already ship with your system (Windows: netsh, route, ipconfig, arp, sc; Linux: nmcli, systemctl, arp). If one isn't present (rare, mostly on minimal Linux), that single tool says so and everything else keeps working.

Two things you install ONLY if you use the tool that needs them:

• Capture (packet analyzer) needs a capture driver — Npcap on Windows (npcap.com, tick "WinPcap API-compatible mode"); Linux uses the built-in libpcap. The tool detects a missing driver and tells you.
• SFTP/SCP receive (in Local servers) uses your OS's OpenSSH server — enable it once (the panel shows the exact commands). A built-in SFTP server is coming in a later release.

Optional: Lab Testing's throughput test needs iperf3 installed on both ends. It isn't bundled or required.

Uninstalling: on Windows, remove SubnetSlinger from Settings → Apps (or the Microsoft Store) — the MSIX package uninstalls cleanly, no separate uninstaller needed. On Linux, delete the unpacked folder (or run the included uninstall.sh). Uninstalling does NOT delete your work — exports, incidents, captures, and settings (including the Vault) stay in Documents/SubnetSlinger and the app's settings folder so you don't lose them by accident; delete those yourself if you want a clean sweep. Npcap and OpenSSH-server, if you added them, are system components you remove separately.