Skip to main content
The VPN agent is available as a pre-configured virtual appliance. You download it from the dashboard, import it into your hypervisor, and boot it. The agent connects to the platform.
VPN profiles require the Internal network scanning add-on.

​
System requirements

​
Downloading the VM

  1. Go to Settings > VPN Profiles
  2. Click on your VPN profile and open the deployment menu
  3. Select Virtual Machine
  4. Download the format that matches your hypervisor:
Each download is pre-configured with your VPN profile credentials.

​
Installation

​
VMware Workstation / Fusion

The .vmdk file is a virtual disk, not a standalone appliance. You need to create a new VM that uses it.
  1. Go to File > New Virtual Machine
  2. Choose Custom configuration
  3. When prompted for the disk, select Use an existing virtual disk and browse to the downloaded .vmdk file
  4. Complete the wizard (Linux / Ubuntu 64-bit, 1+ vCPU, 1+ GB RAM)
  5. Start the VM

​
vSphere / ESXi

  1. Open vSphere Client
  2. Right-click on your datacenter or cluster
  3. Select Deploy OVF Template
  4. Browse to the downloaded file
  5. Follow the deployment wizard, selecting the appropriate datastore and network

​
Network configuration

Connect the VM to a network that has:
  • Outbound internet access (TCP port 22 to vpn2.pentest-tools.com)
  • Access to the internal targets you want to scan
If you need to scan across VLANs, place the agent in a VLAN with routing to your targets, or use a trunk port with the appropriate VLAN access.

​
Verifying the connection

After booting the VM:
  1. The agent starts automatically and connects to the platform
  2. Go to Settings > VPN Profiles and check that your profile shows as Online
  3. Use the Test connection button to verify end-to-end connectivity
The default credentials are root / vpnagent007 and tc / vpnagent007. Change these passwords immediately after the first boot.

​
Network requirements

No inbound ports need to be opened.

​
Assigning a static IP

The agent VM uses DHCP by default. If you need a fixed IP to whitelist the agent on internal firewalls, you can assign one at the terminal. The change does not survive a reboot, so you’ll need to reapply it after each reboot.
In VMware, set the network adapter to Bridged mode, not NAT. NAT hides the VM behind the host IP, which means the agent cannot reach internal targets directly.
Boot the VM, then press Ctrl+C at the agent console to get a shell. Run the following commands with your own network values:
Verify the IP is set:
If both pings succeed, run start to restart the agent.
These settings are lost after a reboot. For a permanent static IP, use a DHCP reservation on your router or DHCP server tied to the VM’s MAC address. That way the VM always gets the same IP without manual steps.