Created on
02-27-2017
03:46 AM
Edited on
01-02-2025
07:50 AM
By
Jean-Philippe_P
Description
Solution
- For SSL VPN configuration refer to the SSL VPN user guide: SSL VPN quick start.
- For Site-to-site IPsec VPN, refer to the IPsec VPN user guide: Site-to-site VPN.
FortiGate A Configuration:
Existing SSL VPN configuration:
- SSL VPN users IP pool: 10.100.100.1 - 10.100.100.14.
- If the split tunnel is enabled, make sure that the LAN B subnet (192.168.1.0/24) is in the access list.
- In this example, SSL VPN users want to access an internal DNS server on the remote side of the IPSec tunnel for internal DNS resolution. DNS server IP can be added by CLI or by GUI as shown below:
- In the CLI:
config vpn ssl settings
set dns-server1 192.168.1.x <- Address of remote DNS Server.
end
- In the GUI:
- Virtual IPSec interface name: ipsec-vpn.
- Add SSL VPN IP range to phase 2 selectors.
Local : 10.1000.100.0/28
Remote : 192.168.1.0/24
- Make sure there is a firewall policy to allow traffic from SSL VPN to the IPsec tunnel.
Note: Ensure SNAT is not set to 'Use Outgoing Interface Address'.
(FortiGate B internal network 192.168.1.0/24)
Action: Accept
FortiGate B Configuration:
Existing IPsec VPN configuration:- Virtual IPSec interface name: FortigateB-vpn.
- Add phase 2 traffic selector.
Local : 192.168.1.0/24
Remote : 10.100.100.0/28
• Make sure there is a firewall policy to allow traffic from the IPsec tunnel to the LAN.
Note: Ensure SNAT is not set to 'Use Outgoing Interface Address'.
• Make sure there is a static route to 10.100.100.0/28 via FortigateB-vpn.