VPN profiles require the Internal network scanning add-on.
Prerequisites
- Docker installed and running
- Outbound connectivity to vpn2.pentest-tools.com on TCP port 22
- Network access to internal targets from the Docker host
Quick start
Pull and run
Run the following command, replacing You can also copy this command directly from the deployment menu in Settings > VPN Profiles.
<VPN_UUID> with your UUID:Required capabilities
The agent needs these Linux capabilities:| Capability | Purpose |
|---|---|
NET_ADMIN | VPN tunnel management |
/dev/net/tun | TUN device for the VPN tunnel |
Network modes
By default, the container uses Docker’s bridge network. Depending on your setup, you may need a different mode.Host network mode
Gives the container direct access to the host’s network interfaces:Custom Docker network
To scan containers in a specific Docker network:Docker Compose
Set your VPN UUID as thecommand in the Compose file:
Replace
<VPN_UUID> with the UUID from your VPN profile.Managing the agent
Troubleshooting
Container exits immediately
Container exits immediately
- Check that the VPN UUID is provided as an argument after the image name
- Verify
--cap-add=NET_ADMINis set - Check that the
/dev/net/tundevice is mounted - Check container logs:
docker logs pentest-agent
Cannot reach internal targets
Cannot reach internal targets
- Verify the container’s network mode allows access to targets
- Check host firewall rules
- Try
--network hostmode