Documentation
Written for someone standing in front of the equipment. Each guide says what you need before you start, and only covers what the software actually does.
Getting started
Install it, get through first launch, add Npcap if you need it.
Installing CySecTek
The installer, the MSI, and verifying what you downloaded before you run it.
First launch and the app password
What the app password protects, why it cannot be recovered, and what to do first.
Installing Npcap
The packet-capture driver that Port Finder and Packet Capture need, and nothing else does.
Connecting to equipment
SSH, keys, serial, and the saved connection list.
Finding things
Switch ports, subnets, open ports, wireless and packets.
Finding the switch port you are plugged into
LLDP and CDP discovery: what it needs, how long it takes, and when it stays empty.
Scanning a subnet and its ports
Sweep a network for hosts, then scan one host or all of them for open ports.
Wi-Fi analysis
Scanning for networks, reading channel congestion, and tracing signal as you walk.
Capturing packets
Filters, what gets decoded, and where this stops being the right tool.
Moving files and staging kit
SFTP, and the temporary TFTP and DHCP servers.
Managing the app
Credentials, exports, upgrades and what to do when something breaks.
Troubleshooting
The errors people actually hit, with the cause rather than a restatement of the symptom.
- Port Finder or Packet Capture says Npcap is missingThe capture driver is not installed. Windows will not show raw frames without it.
- Packet capture starts but sees nothing, or refuses to startWindows only exposes raw capture to an elevated process.
- SSH authentication failedUsually the credential, but on network equipment it is often the account or the method.
- The host key has changed and the connection was refusedThe device is presenting a different key than the one pinned on first connect.
- The private key could not be readUsually a PuTTY .ppk, an encrypted key with no passphrase entered, or a wrong passphrase.
- “No common key exchange algorithm”A version before 0.7.1 against equipment offering older key exchanges.
- The TFTP or DHCP server is running but nothing reaches itWindows Firewall is blocking the inbound traffic, usually because the prompt was dismissed.
- Port Finder hears nothingOften the switch is not advertising — but rule out the cheaper causes first.
- The serial port will not open, or is already in useWindows gives a COM port to whoever opened it first.
- An adapter disappeared, or results are empty after unplugging somethingThe view is bound to an adapter that no longer exists.
- No wireless networks are listed, or scanning is blockedWindows requires Location Services before it returns scan results to an application.
- An update failed to verifyThe downloaded package did not match the expected hash, so it was discarded.
- Saved passwords will not decrypt, or the credential store looks corruptedEither the wrong app password, or a store written by a key that no longer exists.