Quick-Start Guide
Quick-Start Guide
Prefer the PDF version? Download PacketPilot-QuickStart.pdf — same content, formatted for print.
This guide walks you through getting PacketPilot Config and PacketPilot Analyze running in a lab environment with a network switch or router. Estimated time: 30 minutes.
Before You Start
You will need:
- A Windows PC (10 or 11, 64-bit)
- A network device (switch or router) with SSH access — Cisco IOS recommended for first-time use
- A USB-to-serial console cable (optional but recommended)
- Docker Desktop installed on Linux or WSL2 (for Analyze)
Part 1: Install PacketPilot Config
-
Download the ZIP archive:
https://packetpilot.db-electronics.no/api/download/exe -
Extract the ZIP to a permanent location (e.g.
C:\PacketPilot) -
Open the extracted folder and run
PacketPilot Config.exe -
On first launch, create a master password — this protects your stored credentials
-
The 30-day trial starts automatically
Why a ZIP instead of a direct EXE? Windows marks downloaded files with a security restriction that can prevent the app's DLLs from loading. Extracting the ZIP avoids this — the EXE inside runs cleanly without any "Unblock" step.
Part 2: Connect to a Device via SSH
Add the Device
- Open the Inventory tab
- Click Add Device
- Enter the device IP address (e.g.
192.168.1.1) - Select the vendor: Cisco (or Auto-detect)
- Enter SSH username and password
- Click Save
Config tests the connection immediately. If successful, the device appears in the inventory.
Open an SSH Session
Double-click the device in the inventory. An SSH terminal opens in the Sessions tab.
Try some read-only commands:
show version
show interfaces status
show vlan brief
Part 3: Connect via Serial Console (Optional)
If you prefer console access (e.g. for initial device setup):
- Connect the USB-to-serial cable from your PC to the device console port
- Note the COM port number in Windows Device Manager
- In Config, open the Console tab
- Select the COM port and vendor profile (e.g. Cisco)
- Click Connect
- Press Enter — you should see the device prompt
Part 4: Run the Cisco Bootstrap Wizard
Note: The bootstrap wizard applies actual configuration to the device. Only use this on a test device or in a lab environment.
- Connect to the device via console (see Part 3)
- With the Cisco profile selected, click Bootstrap in the Console tab
- Follow the wizard steps:
| Step | Example Value |
|------|--------------|
| Hostname | SW-CORE-01 |
| Management VLAN | 1 |
| IP Address | 192.168.1.10 |
| Subnet Mask | 255.255.255.0 |
| Default Gateway | 192.168.1.1 |
| Enable Secret | MySecretPass! |
- Review the generated commands in the preview panel
- Click Apply — commands are sent to the device over the serial connection
- When complete, SSH to the new management IP to verify
Part 5: Install PacketPilot Analyze
Linux / WSL2
mkdir -p ~/packetpilot-analyze
cd ~/packetpilot-analyze
unzip ~/Downloads/PacketPilot-Analyze-Suite.zip
cp .env.example .env
docker compose up -d
Verify Services
docker compose ps
All services should show Up. Open the web UI at http://localhost:3000.
Download the Ollama Model
docker compose logs -f ollama
# Wait for "pulling model... done" then Ctrl+C
Part 6: Run Your First Analysis
1. Create a Capture File
On your network device, capture a short segment of traffic:
show interfaces
show access-lists
show running-config
Save the output as a .txt file.
Or, if you have a .pcap file from Wireshark or a span port, use that directly.
2. Create a Case in Analyze
- Open
http://localhost:3000 - Click New Case
- Name it (e.g.
Test-Case-01) - Click Create
3. Upload and Analyze
- Click Upload Artifact
- Select your capture file
- Click Analyze
Findings appear in the Findings tab. AI explanations appear in the AI Summary tab.
4. Export a PDF Report
Click Export PDF in the case toolbar to download a human-readable report.
Part 7: Export Config Findings to Analyze
In Config:
- Right-click a device → Export Findings
- Choose JSON format
- Save the file
In Analyze:
- Open or create a case
- Click Upload Artifact
- Select the JSON file
- Click Analyze
The findings from Config are imported directly into the Analyze case.
Next Steps
- Config User Guide — full documentation for Config
- Analyze User Guide — full documentation for Analyze
- Architecture Overview — understand how the two products fit together
Getting Help
Stuck on something? Email support@db-electronics.no.