Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
@zachartl you can certainly share the same connection profile/tunnel-group. You can use authorisation via LDAP/RADIUS to dynamically assign group-policy, access-list or split-tunneling settings based on AD group membership.
@s_SiD_s use the same policy set for all VPN connections, but create multiple authorisation rules (not authentication) and define the AD Group as one of the conditions. If you are still having issues provide a screenshot of your authorisation rules.
@knanyhy011 use a loopback instead of statically assigning the IP address to the virtual-template, as directly assigning a static IP address and subnet mask to a Virtual Template Interface is not supported. https://www.cisco.com/c/en/us/td/docs/route...
@sahdogra I am aware of what you are trying to achieve.
When you define the protected networks you define your source "10.0.0.0" and the remote protected network "192.168.0.0", traffic from 10.0.0.0 not going to 192.168.0.0 will not be encrypted and ...
@sahdogra
Example https://www.cisco.com/c/en/us/td/docs/security/asa/asa924/configuration/vpn/asa-924-vpn-config/vpn-site2site.html#ID-2445-000001fe on FTD it's referred to as "Protected Network" which represents the networks to be encrypted. If the...