Linux Deployment for OTserver and the Scanner

Linux prerequisites

Use a dedicated scanner account, a selected physical interface, and either root or CAP_NET_RAW for Linux AF_PACKET discovery. Keep output and SNMP profiles in a restricted directory.

Build and inspect the scanner

Build and inspect the scanner:

1
2
3

cargo build --release
sudo ./target/release/otserver-scanner doctor
sudo ./target/release/otserver-scanner interfaces

Linux scan

1
2
3
4
5
6

sudo ./target/release/otserver-scanner scan \
  --target 192.168.1.0/24 \
  --interface eth0 \
  --source-mac 00:11:22:33:44:55 \
  --output ./scan.otserver.json \
  --ack-authorized

Linux uses a native AF_PACKET raw socket for PROFINET and needs root or CAP_NET_RAW. Disable protocols individually with flags such as --no-profinet or --no-snmp; there is no --read-only switch because read-only behavior is the scanner’s design boundary.

Verify the result

Validate the export before importing it:

1

./target/release/otserver-scanner validate ./scan.otserver.json

Exit code 0 means complete valid output, 2 means valid output with partial failures, and 1 means no valid output.

Configure a weekly plant scan or review the protocol requests.