Skip to main content
Can I use a TheGreenBow IKEv1 connection with VPN Tracker? - KH2264

Frequently Asked Questions

Can I use a TheGreenBow IKEv1 connection with VPN Tracker?
 

Yes, this is possible. You can migrate an existing TheGreenBow IKEv1 connection to VPN Tracker by exporting the relevant connection data and manually entering it into VPN Tracker.

How to extract the required information:

  1. Open TheGreenBow and select the desired connection.
  2. Open the configuration menu and choose “Export”.
  3. In the next dialog, enable “Do not protect exported VPN configuration” to export the data in plain text.
  4. Save the file to a location of your choice.

Key information needed in VPN Tracker:

1. Gateway Address

The IP address or hostname of your VPN endpoint. In TheGreenBow, this is listed as “Remote VPN Gateway”.

2. Remote Networks

In VPN Tracker, you must define which networks should be reachable through the VPN tunnel. These are called Remote Networks or Target Networks, and correspond to:

  • Phase 2 > Network Configuration
  • Remote LAN / Remote Network

Typical entries include:

  • 192.168.1.0/24 – a full subnet
  • 10.0.0.0/16 – a larger network range
  • 172.16.0.10/32 – a single host

Enter these under the “Remote Networks” or “Target Networks” section in VPN Tracker. Ensure these match the configuration on the VPN gateway, otherwise traffic might not be routed correctly.

Tip: If you're unsure, use 0.0.0.0/0 as a temporary setting. This allows access to all remote networks (if permitted). You can restrict this later as needed.

3. Preshared Key (PSK)

If you don’t already have the PSK, you can find it in the exported file under the “Authentication” section.

4. XAuth Credentials

Username and password for extended authentication (if used).

5. Local ID and Remote ID

These values define the identities of both VPN peers during the IKE handshake. They are especially important if:

  • the VPN gateway doesn’t identify by IP address (e.g. due to NAT or dynamic IPs),
  • certificates or advanced authentication profiles are used,
  • the gateway expects a specific identity (e.g. FQDN or custom ID).

In the exported file, these are typically found under “ID Type”, “Local ID”, and “Remote ID”.
Enter them in VPN Tracker under “Identifiers” > Local / Remote, and use the correct format (e.g. FQDN, email address, Key ID, or IP address).

6. Encryption and Authentication Settings

Pay close attention to the algorithms used for Encryption, Authentication, and Hashing, and replicate them in VPN Tracker under Phase 1 and Phase 2 settings.

Privacy Settings / Datenschutz-Einstellungen