Repository navigation
Command Line Interface
knoxxr edited this page Jul 14, 2026
·
1 revision
NetworkScanner.Cli is a headless, cross-platform console front-end (netscan) over the same NetworkScanner.Core engine — for servers, SSH sessions, cron jobs, and pipelines where no GUI is available.
Progress is written to stderr and final results to stdout, so JSON output is safe to pipe.
# From source
dotnet run --project NetworkScanner.Cli -- --range 192.168.1.0/24 --ports 22,80,443
# Or the released single-file binary
./netscan --range 10.0.0.0/24 -o json --out scan.json
./netscan # scan the auto-detected local subnet, table output| Option | Description |
|---|---|
--range <CIDR|start-end|ip> |
Target(s) to scan. Repeatable. Defaults to the local subnet if omitted. |
--ports 22,80,443 |
Comma-separated TCP ports to check. |
-o table|json|csv |
Output format (default table). |
--out <file> |
Write output to a file instead of stdout. |
--lang en|ko |
UI/message language. |
-q |
Quiet — suppress progress on stderr. |
--help |
Full option list. |
- The same vendor / OS / service detection and reserved / backdoor-port matching as the GUI are applied.
- Because progress goes to stderr and results to stdout,
netscan --range 10.0.0.0/24 -o json > scan.jsonproduces clean JSON with progress still visible in the terminal. - On Linux/macOS, ICMP ping may need elevated permission — see Troubleshooting & FAQ.