Fortinet Document Library

Version:


Table of Contents

Cookbook

6.2.0
Download PDF
Copy Link

SSL VPN to IPsec VPN

This is a sample configuration of site-to-site IPsec VPN that allows access to the remote endpoint via SSL VPN.

This example uses a pre-existing user group, a tunnel mode SSL VPN with split tunneling, and a route-based IPsec VPN between two FortiGates. All sessions must start from the SSL VPN interface.

If you want sessions to start from the FGT_2 subnet, you need more policies. Also, if the remote subnet is beyond FGT_2 (if there are multiple hops), you need to include the SSL VPN subnet in those routers as well.

Sample topology

Sample configuration

To configure the site-to-site IPsec VPN on FGT_1:
  1. Go to VPN > IPsec Wizard.
  2. In the VPN Setup pane:
    1. Specify the VPN connection Name as to_FGT_2.
    2. Select Site to Site.
    3. Click Next.

  3. In the Authentication pane:
    1. Enter the IP Address to the Internet-facing interface.
    2. For Authentication Method, click Pre-shared Key and enter the Pre-shared Key.
    3. Click Next.

  4. In the Policy & Routing pane:
    1. Set the Local Interface to the internal interface.
    2. Set the Local Subnets to include the internal and SSL VPN subnets for FGT_1.
    3. Set Remote Subnets to include the internal subnet for FGT_2.
    4. Click Create.

A confirmation screen shows a summary of the configuration including the firewall address groups for both the local and remote subnets, static routes, and security policies.

To configure SSL VPN settings:
  1. Go to VPN > SSL-VPN Settings.
  2. Set Listen on Interface(s) to wan1.
  3. To avoid port conflicts, set Listen on Port to 10443.
  4. For Restrict Access, select Allow access from any host.
  5. In the Tunnel Mode Client Settings section, select Specify custom IP ranges and include the SSL VPN subnet range created by the IPsec Wizard.
  6. In the Authentication/Portal Mapping section, add the VPN user group to the tunnel-access Portal. Set All Other Users/Groups to the web-access Portal.

  7. Click Apply.
To configure SSL VPN portal:
  1. Go to VPN > SSL-VPN Portals.
  2. Select tunnel-access and click Edit.
  3. Turn on Enable Split Tunneling so that only traffic intended for the local or remote networks flow through FGT_1 and follows corporate security profiles.
  4. For Routing Address, add the local and remote IPsec VPN subnets created by the IPsec Wizard.
  5. For Source IP Pools, add the SSL VPN subnet range created by the IPsec Wizard.

  6. Click OK.
To add policies to FGT_1:
  1. Go to Policy & Objects > IPv4 Policy.
  2. Click Create New to create a policy that allows SSL VPN users access to the IPsec VPN tunnel.
  3. For Incoming Interface, select ssl.root.
  4. For Outgoing Interface, select the IPsec tunnel interface to_FGT_2.
  5. Set the Source to all and the VPN user group.
  6. Set Destination to the remote IPsec VPN subnet.
  7. Specify the Schedule.
  8. Set the Service to ALL.
  9. In the Firewall/Network Options section, disable NAT.

  10. Click OK.
To configure the site-to-site IPsec VPN on FGT_2:
  1. Go to VPN > IPsec Wizard.
  2. In the VPN Setup pane:
    1. Specify the VPN connection Name as to FGT_1.
    2. Select Site to Site.
    3. Click Next.

  3. In the Authentication pane:
    1. Enter the IP Address to the Internet-facing interface.
    2. For Authentication Method, click Pre-shared Key and enter the Pre-shared Key of the FGT_1.
    3. Click Next.

  4. In the Policy & Routing pane:
    1. Set the Local Interface to the internal interface.
    2. Set the Local Subnets to include the internal and SSL VPN subnets for FGT_2.
    3. Set Remote Subnets to include the internal subnet for FGT_1.
    4. Click Create.

A confirmation screen shows a summary of the configuration including the firewall address groups for both the local and remote subnets, static routes, and security policies.

To check the results:
  1. Go to Monitor > IPsec Monitor.
  2. Select the tunnel and click Bring Up.

  3. Verify that the Status changes to Up.

  4. Configure the SSL VPN connection on the user's FortiClient and connect to the tunnel.

  5. On the user's computer, use CLI to send a ping though the tunnel to the remote endpoint to confirm access.

  6. Go to Monitor > Routing Monitor and verify that the routes for the IPsec and SSL VPNs are added.

  7. Go to Monitor > SSL-VPN Monitor and verify user connectivity.

  8. Go to Log & Report > Events and view the IPsec and SSL tunnel statistics.

  9. Go to VPN > VPN Location Map and view VPN connection activity.

  10. Go to FortiView > Policies and view policy usage.

Troubleshooting

To troubleshoot on FGT_1, use the following CLI commands:
diag debug reset
diag debug flow show function-name enable
diag debug flow show iprope enable
diag debug flow filter addr 172.16.200.55
diag debug flow filter proto 1
diag debug flow trace start 2
diag debug enable
To troubleshoot using ping:
  1. Send a ping through the SSL VPN tunnel to 172.16.200.55 and analyze the output of the debug.
  2. Disable the debug output with this command: diag debug disable.

If traffic is entering the correct VPN tunnel on FGT_1, then run the same commands on FGT_2 to check whether the traffic is reaching the correct tunnel. If it is reaching the correct tunnel, confirm that the SSL VPN tunnel range is configured in the remote side quick mode selectors.

To troubleshoot using a sniffer command:
diag sniff packet any "host 172.16.200.44 and icmp" 4
To troubleshoot IPsec VPN issues, use the following commands on either FortiGate:
diag debug reset
diag vpn ike gateway clear
diag debug application ike -1
diag debug enable

SSL VPN to IPsec VPN

This is a sample configuration of site-to-site IPsec VPN that allows access to the remote endpoint via SSL VPN.

This example uses a pre-existing user group, a tunnel mode SSL VPN with split tunneling, and a route-based IPsec VPN between two FortiGates. All sessions must start from the SSL VPN interface.

If you want sessions to start from the FGT_2 subnet, you need more policies. Also, if the remote subnet is beyond FGT_2 (if there are multiple hops), you need to include the SSL VPN subnet in those routers as well.

Sample topology

Sample configuration

To configure the site-to-site IPsec VPN on FGT_1:
  1. Go to VPN > IPsec Wizard.
  2. In the VPN Setup pane:
    1. Specify the VPN connection Name as to_FGT_2.
    2. Select Site to Site.
    3. Click Next.

  3. In the Authentication pane:
    1. Enter the IP Address to the Internet-facing interface.
    2. For Authentication Method, click Pre-shared Key and enter the Pre-shared Key.
    3. Click Next.

  4. In the Policy & Routing pane:
    1. Set the Local Interface to the internal interface.
    2. Set the Local Subnets to include the internal and SSL VPN subnets for FGT_1.
    3. Set Remote Subnets to include the internal subnet for FGT_2.
    4. Click Create.

A confirmation screen shows a summary of the configuration including the firewall address groups for both the local and remote subnets, static routes, and security policies.

To configure SSL VPN settings:
  1. Go to VPN > SSL-VPN Settings.
  2. Set Listen on Interface(s) to wan1.
  3. To avoid port conflicts, set Listen on Port to 10443.
  4. For Restrict Access, select Allow access from any host.
  5. In the Tunnel Mode Client Settings section, select Specify custom IP ranges and include the SSL VPN subnet range created by the IPsec Wizard.
  6. In the Authentication/Portal Mapping section, add the VPN user group to the tunnel-access Portal. Set All Other Users/Groups to the web-access Portal.

  7. Click Apply.
To configure SSL VPN portal:
  1. Go to VPN > SSL-VPN Portals.
  2. Select tunnel-access and click Edit.
  3. Turn on Enable Split Tunneling so that only traffic intended for the local or remote networks flow through FGT_1 and follows corporate security profiles.
  4. For Routing Address, add the local and remote IPsec VPN subnets created by the IPsec Wizard.
  5. For Source IP Pools, add the SSL VPN subnet range created by the IPsec Wizard.

  6. Click OK.
To add policies to FGT_1:
  1. Go to Policy & Objects > IPv4 Policy.
  2. Click Create New to create a policy that allows SSL VPN users access to the IPsec VPN tunnel.
  3. For Incoming Interface, select ssl.root.
  4. For Outgoing Interface, select the IPsec tunnel interface to_FGT_2.
  5. Set the Source to all and the VPN user group.
  6. Set Destination to the remote IPsec VPN subnet.
  7. Specify the Schedule.
  8. Set the Service to ALL.
  9. In the Firewall/Network Options section, disable NAT.

  10. Click OK.
To configure the site-to-site IPsec VPN on FGT_2:
  1. Go to VPN > IPsec Wizard.
  2. In the VPN Setup pane:
    1. Specify the VPN connection Name as to FGT_1.
    2. Select Site to Site.
    3. Click Next.

  3. In the Authentication pane:
    1. Enter the IP Address to the Internet-facing interface.
    2. For Authentication Method, click Pre-shared Key and enter the Pre-shared Key of the FGT_1.
    3. Click Next.

  4. In the Policy & Routing pane:
    1. Set the Local Interface to the internal interface.
    2. Set the Local Subnets to include the internal and SSL VPN subnets for FGT_2.
    3. Set Remote Subnets to include the internal subnet for FGT_1.
    4. Click Create.

A confirmation screen shows a summary of the configuration including the firewall address groups for both the local and remote subnets, static routes, and security policies.

To check the results:
  1. Go to Monitor > IPsec Monitor.
  2. Select the tunnel and click Bring Up.

  3. Verify that the Status changes to Up.

  4. Configure the SSL VPN connection on the user's FortiClient and connect to the tunnel.

  5. On the user's computer, use CLI to send a ping though the tunnel to the remote endpoint to confirm access.

  6. Go to Monitor > Routing Monitor and verify that the routes for the IPsec and SSL VPNs are added.

  7. Go to Monitor > SSL-VPN Monitor and verify user connectivity.

  8. Go to Log & Report > Events and view the IPsec and SSL tunnel statistics.

  9. Go to VPN > VPN Location Map and view VPN connection activity.

  10. Go to FortiView > Policies and view policy usage.

Troubleshooting

To troubleshoot on FGT_1, use the following CLI commands:
diag debug reset
diag debug flow show function-name enable
diag debug flow show iprope enable
diag debug flow filter addr 172.16.200.55
diag debug flow filter proto 1
diag debug flow trace start 2
diag debug enable
To troubleshoot using ping:
  1. Send a ping through the SSL VPN tunnel to 172.16.200.55 and analyze the output of the debug.
  2. Disable the debug output with this command: diag debug disable.

If traffic is entering the correct VPN tunnel on FGT_1, then run the same commands on FGT_2 to check whether the traffic is reaching the correct tunnel. If it is reaching the correct tunnel, confirm that the SSL VPN tunnel range is configured in the remote side quick mode selectors.

To troubleshoot using a sniffer command:
diag sniff packet any "host 172.16.200.44 and icmp" 4
To troubleshoot IPsec VPN issues, use the following commands on either FortiGate:
diag debug reset
diag vpn ike gateway clear
diag debug application ike -1
diag debug enable