Skip to main content
HS08
Valued Contributor
October 27, 2026
Solved

IPsec VPN RA

When we migrate from SSL VPN to IPsec VPN, we currently use different firewall policies based on user groups to separate access for each vendor. In that case, would the firewall policies be configured as follows?

config firewall policy
    edit 1
        set name "vendor1"
        set uuid xxx
        set srcintf "ssl.Internet"
        set dstintf "Internal"
        set action accept
        set srcaddr "SSLVPN_TUNNEL_ADDR1"
        set dstaddr "SERVER1"
        set schedule "always"
        set service "RDP"
        set utm-status enable
        set logtraffic all
        set groups "vendor1"
    next

edit 2
        set name "vendor2"
        set uuid xxx
        set srcintf "ssl.Internet"
        set dstintf "Internal"
        set action accept
        set srcaddr "SSLVPN_TUNNEL_ADDR1"
        set dstaddr "SERVER2"
        set schedule "always"
        set service "RDP"
        set utm-status enable
        set logtraffic all
        set groups "vendor2"
    next
end

 

But if we use IPsec VPN, do we need to create separate IPsec profiles and assign each profile to a different client IP address range based on the user group? Also, would the firewall policies then be applied only based on the client IP address range?

 edit "vpn-vendor1"
        set type dynamic
        set interface "port2"
        set local-gw xxx
        set mode aggressive
        set peertype one
        set net-device disable
        set mode-cfg enable
        set ipv4-dns-server1 10.10.10.10
        set proposal aes256-sha256 aes128-sha1
        set dpd on-idle
        set dhgrp 20 5
        set xauthtype auto
        set authusrgrp "vendor1"
        set ipv4-start-ip 10.20.1.10
        set ipv4-end-ip 10.20.1.200
        set ipv4-split-include "10.0.0.0/8"
        set unity-support disable
        set dpd-retryinterval 60
    next

 

edit "vpn-vendor2"
        set type dynamic
        set interface "port2"
        set local-gw xxx
        set mode aggressive
        set peertype one
        set net-device disable
        set mode-cfg enable
        set ipv4-dns-server1 10.10.10.10
        set proposal aes256-sha256 aes128-sha1
        set dpd on-idle
        set dhgrp 20 5
        set xauthtype auto
        set authusrgrp "vendor2"
        set ipv4-start-ip 10.20.2.10
        set ipv4-end-ip 10.20.2.200
        set ipv4-split-include "10.0.0.0/8"
        set unity-support disable
        set dpd-retryinterval 60
    next

 

In short, when using SSL VPN, we only need one SSL VPN profile for all user groups. However, with IPsec VPN, does each group need its own IPsec profile?

HS08
HS08Answer
Valued Contributor
October 27, 2026

Thanks

3 replies

funkylicious
SuperUser
SuperUser
October 27, 2026

the policies would have the srcintf the phase-1 name , meaning vpn-vendor1 and vpn-vendor2 and not ssl.internet

if you create multiple ipsec dialup tunnels, to make sure that each user/vendor hits the correct tunnel ( each tunnel should have its unique PSK as best practice ) you need to differenciate between then using a peer id for ikev1 and each ipsec should have it’s unique range of IP’s that would get assigned to the dialup clients. 

also, you have to use one of the options for where you specify the group, either in the ipsec config or in the firewall rule, cannot be both - 

 

"jack of all trades, master of none"
HS08
HS08AuthorAnswer
Valued Contributor
October 27, 2026

Thanks

Toshi_Esumi
SuperUser
SuperUser
October 27, 2026

If only for policies (means split-tunneling is the same between those groups just like your situation) you can use the same phase1 for both groups.
However, you need to keep “set authgroup” (empty) or null “” in the phase1 config.

Toshi

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT