Step 7: Verifying the VPN Tunnel

Jamf Connect Documentation

Solution
Application
Jamf Connect
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US
  1. To start the VPN service, enter the following in the Quick Connect Linux VM command line:
    sudo service strongswan-starter restart
    
  2. Verify whether the VPN tunnel is working:
    1. Enter sudo ipsec statusall in the command line to verify that the service is up and running correctly.
      Note:

      If you receive an error or nothing is returned, enter sudo service strongswan-starter start and correct any issues indicated. Then repeat the sudo service strongswan-starter start command until the service starts successfully and sudo ipsec statusall returns a result that isn't blank and doesn't indicate any errors.

    2. Set up an Enterprise Application in Jamf Security Cloud under Policies > Access > Access Policy that is configured to route via the Gateway corresponding to this Quick Connect VM.
      Note:

      Ensure that the hostname you are defining in the access policy resolves to the IP of a server on the inside of the network. If this hostname is not publicly resolvable, either add the custom IP for each hostname, or publish a hostname using a public DNS service.

    3. Try to access the application from a browser or native app on a device registered with WPA that is also authorized to use the application that you just created.

      The application should load if all the settings are correctly configured.

    4. Enter sudo ipsec statusall on the Quick Connect Linux VM to view the new security association, which indicates that the VPN tunnel is now up and running.
    Note:

    If the tunnel is in an active state but traffic is not properly routing, click Access Gateways in Jamf Security Cloud, then select the gateway and click Logs to display errors and remediation steps.

Your VPN is configured and ready for use.

You can create Access Policies to define the applications your users can access. For more information, see Zero Trust Network Access Policy.