This guide shows common command patterns for nrev.
Replace example targets with systems you own or are authorized to test.
Usage: nrev <COMMAND>
Commands:
port Scan ports and collect structured observations
task Run a port-scan task from a JSON or TOML file
host Discover reachable hosts with ICMP, UDP, or TCP probes
ping Send repeated probes to a target with ICMP, UDP, TCP, or QUIC
trace Trace the path to a target with UDP or ICMP probes
nei Discover a neighbor with ARP or NDP
probe Show the built-in and externally loaded probe catalog
recipe Show externally loaded scan recipes
Basic TCP scan:
nrev port 192.168.10.10
nrev port 192.168.10.10 --ports 22,80,443,3389
nrev port 192.168.10.0/24 --ports top-100Supported named port sets:
nrev port 192.168.10.10 --ports top-100
nrev port 192.168.10.10 --ports top-1000
nrev port 192.168.10.10 --ports well-knownUDP scan:
nrev port 192.168.10.10 --transport udp --ports 53,123SYN scan:
nrev port 192.168.10.10 --transport syn --ports 22,80,443
nrev port 192.168.10.0/24 --transport syn --ports top-100QUIC scan:
nrev port edge.example --transport quic --ports 443,8443Host-and-port input:
nrev port 192.168.10.10:443Show closed and filtered states in the human-readable report:
nrev port 192.168.10.10 --ports 22,80,443 --all-statesWrite JSON output:
nrev port 192.168.10.10 --format json --output result.jsonBasic reachability scan:
nrev host 192.168.10.0/24TCP-based discovery on selected ports:
nrev host yourcorpone.com --method tcp --ports 80,443UDP-based discovery:
nrev host 192.168.10.0/24 --method udp --ports 33434,40125Read targets from a file:
nrev host @./targets.txt --method tcp --ports 80,443Show unreachable hosts in the human-readable report:
nrev host 192.168.10.0/24 --all-hostsWrite JSON output:
nrev host 192.168.10.0/24 --format json --output hosts.jsonBasic ICMP ping:
nrev ping 192.168.10.10UDP, TCP, and QUIC ping:
nrev ping example.com --method udp --port 33435
nrev ping example.com --method tcp --port 443
nrev ping example.com --method quic --port 443Tune probe count and timing:
nrev ping example.com --count 5 --interval-ms 250 --timeout-ms 1500Write JSON output:
nrev ping example.com --format json --output ping.jsonBasic UDP trace:
nrev trace example.comICMP trace:
nrev trace example.com --method icmpTune hop limit and timeout:
nrev trace example.com --max-hops 20 --interval-ms 250 --timeout-ms 1200Write JSON output:
nrev trace example.com --format json --output trace.jsonAuto-select ARP for IPv4 and NDP for IPv6:
nrev nei 192.168.10.1
nrev nei fe80::1 --interface en0Force a method explicitly:
nrev nei 192.168.10.1 --method arp
nrev nei fe80::1 --method ndp --interface en0Write JSON output:
nrev nei 192.168.10.1 --format json --output neighbor.jsonQuiet mode:
nrev port 192.168.10.10 --quietExplicit progress mode:
nrev port 192.168.10.10 --progress verboseTune timeout and retry behavior:
nrev port 192.168.10.10 --connect-timeout-ms 1200 --probe-timeout-ms 3000 --retries 1Load a profile file:
nrev port 192.168.10.10 --profile ./tmp/manual-tests/profile-web.tomlCLI flags override profile values:
nrev port 192.168.10.10 --profile ./tmp/manual-tests/profile-web.toml --ports 80,443List sample recipes:
nrev recipe --data ./samples/recipesRun a built-in sample recipe:
nrev port 192.168.10.10 --data ./samples/recipes --recipe web-balanced
nrev port 192.168.10.0/24 --data ./samples/recipes --recipe fast-syn-triageCommand-line targets and recipe selection remain supported:
nrev port 192.168.10.10 --data ./samples/recipes --recipe web-balancedRun a task file that includes its own targets and scan settings:
nrev task ./samples/tasks/web-balanced.tomlExample task file:
name = "web-balanced"
targets = ["192.168.10.10", "@./targets.txt"]
data = "../recipes"
recipe = "web-balanced"
format = "json"
output = "./web-balanced-report.json"Task files support the same port-scan settings as nrev port, including:
targetsortargetportstransportinterfaceconcurrencyconnect_timeout_msprobe_timeout_mshttp_body_preview_bytesretriesprobesbuiltin_probesprofiledatarecipeall_statesquietprogressformatoutput
Relative paths in profile, data, and output are resolved from the task file location.
Show probes from a mixed data-pack directory:
nrev probe --data ./samples/data-packShow recipes from the bundled JSON pack:
nrev recipe --data ./samples/data-pack/pack.json --jsonRun a scan with an external recipe:
nrev port 192.168.10.10 --data ./samples/data-pack --recipe corp-web-alt
nrev port 192.168.10.130 --data ./samples/data-pack/pack.json --recipe corp-quicRun only external probes:
nrev port 192.168.10.10 --ports 8080,8088 --data ./samples/data-pack --probes corp-http-alt --no-builtin-probesCommon short forms:
nrev port 192.168.10.10 -p 80,443 -t tcp -c 128 -q -f json -o result.json
nrev host 192.168.10.0/24 -m tcp -p 80,443 -c 128 -t 1200 -f json -o hosts.json
nrev ping example.com -m tcp -p 443 -c 5 -t 1500 -f json -o ping.json
nrev trace example.com -m icmp -t 1200 -f json -o trace.json
nrev nei 192.168.10.1 -m arp -t 1000 -f json -o neighbor.json
nrev probe -d ./samples/data-pack -j
nrev recipe -d ./samples/recipes -j