Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Mohammed_Omar
New Contributor

IPSEC Dial Up VPN and Firewall Policy Rule

Hello,

 

In the case of an IPSEC dial up VPN, can you select a user group in "Destination" in fortigate latest version (7.6.3) firewall policy ? I can't seem to have it for either IPSEC dial up VPN or SSL VPN in my fortigate (7.4.3). I can choose a user group only for the source.

 

Thank you

10 REPLIES 10
funkylicious
SuperUser
SuperUser

you should be able to choose the group that is used for ipsec or sslvpn where the interface for ipsec or sslvpn is used.

if it's used as a source interface, then as a source and viceversa.

"jack of all trades, master of none"
"jack of all trades, master of none"
Mohammed_Omar
New Contributor

Sorry but in the case of a destination, i cant (i can only choose from address and service, no "user") even if the interface is the correct one.

funkylicious

for destination, it would make sense for the user to not be required only the IP address.

"jack of all trades, master of none"
"jack of all trades, master of none"
Yurisk
SuperUser
SuperUser

No, you cannot, neither in 7.6.3 nor in any FortOS version, and never could. Which means you are trying to achieve some goal in a wrong way, why would you need User Group as the destination? Tell us the final result you are trying to achieve. 

https://yurisk.info
https://yurisk.info
Mohammed_Omar

Well if you have one IPSEC tunnel for a group that is formed by subgroups, you would like to filter in policy rules based on source as much as based on destination. for example :

IPSEC tunnel subnet of Big group A.

Group A contains small groups B and C.

If you want to add a policy rule allowing from IPSEC subnet group A to IPSEC subnet group A you cant because in the destination part there is no choosing user group.

ede_pfau

Then split the policy into multiple ones, using group B in the source field. This makes the policy specific to this usergroup.

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Yurisk

What @ede_pfau said - you can separate users into groups:

  • User A in user group A_group, bound to IPSec tunnel interface Tunnel_A
  • User B in user group B_Group, bound to IPSec tunnel interface Tunnel_B

Then you have two independent IPSEc tunnel interfaces with separate user groups behind each, and now you can create security rules as between any networks behind FGT as usual. Still, you won't be able to use user groups in destination. 

 

https://yurisk.info
https://yurisk.info
knaveenkumar
Staff
Staff

Hi team,
only in the source you can choose user group
-Naveen 

volekbo8
New Contributor

Yes, I remembered that if I change something on the Tunnel side on FG, I should also change it in the same way on FortiClient. What surprised me the most was when I changed from IKEv1 Aggressive to IKEv2 there were no logs on the FortiGate side. It was as if there was no connection between my computer and FortiGate at all.

https://omegle.onl/ vshare
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors