What & why
netwp scan accepts --ports=22,80,443 to probe a custom TCP set, but the single-device netwp ports <ip> always uses the curated default. Allowing the same flag there makes it useful for checking a specific service on one host.
Where
cmd/netwp/scan.go (runPorts), reusing the existing parsePorts / portsFlag helpers.
Scope
- When
--ports=<list> is present, probe that set instead of the default; otherwise unchanged.
- Works with
--json too. Document in help text and both READMEs.
Acceptance
netwp ports 192.168.1.1 --ports=22,443 probes only those.- Full verify suite clean.
Good first issue: reuses parsePorts; small wiring change.
What & why
netwp scanaccepts--ports=22,80,443to probe a custom TCP set, but the single-devicenetwp ports <ip>always uses the curated default. Allowing the same flag there makes it useful for checking a specific service on one host.Where
cmd/netwp/scan.go(runPorts), reusing the existingparsePorts/portsFlaghelpers.Scope
--ports=<list>is present, probe that set instead of the default; otherwise unchanged.--jsontoo. Document in help text and both READMEs.Acceptance
netwp ports 192.168.1.1 --ports=22,443probes only those.Good first issue: reuses
parsePorts; small wiring change.