Just need someone to verify this..
The command " sysopt connection permit-vpn" tells the ASA to allow the VPN traffic regardless of access-lists, correct?
and I can choose not to use this command and control the traffic on the outside access list?
Thanks in advance!
Solved! Go to Solution.
The outside ACL will only check VPN traffic if you remove the sysopt command.
If you remove the sysopt command, the outside ACL will get the hitcounts incrementing for incoming traffic that matches the ACL (even if it's VPN).
However, I don't have an ASA handy to test it.
I am not using the Sysopt command, and I am not seeing hit counts, but it appears to be working. Also with the filters, do they only allow traffic the way you write the ACL?, or do they just apply to inbound traffic from the remote side?
yes that's correct.
For traffic that enters the security appliance through a VPN tunnel and is then decrypted, use the sysopt connection permit-vpn command in global configuration mode to allow the traffic to bypass interface access lists. Group policy and per-user authorization access lists still apply to the traffic.
The vpn-filter has to be applied bidirectionally.
Take a look:
Does this command ONLY bypass JUST the ACL on the interface or does it bypass service policies? With this command enabled, would it also bypass the global service policy?
It will just bypass the ACL applied on the interface where you terminate the VPN (typically your outside interface). Service policy will still be applied to the VPN traffic.
Here is the command reference on "sysopt connection permit-vpn":
Hope that helps.
I just want something cleared...
If I terminate VPN on the outside interface, it will bypass only OUTSIDE interface...
If I apply some access-group on the INSIDE interface OUT it will still block undesired traffic from VPN?
Yes, you are absolutely correct.
Or alternatively, you can also configure "vpn-filter" to only allow specific traffic from remote VPN Client access.
Please mark it as answered, if your querry is resolved. Appreciate your time!
Please do rate the helpful discussion, as that helps us to serve you better!!
Community Manager- Security & VPN
One simple question.
When i disable the command "sysopt connection permit-vpn" the negociation traffic(acl exchange over the Firewalls) in phase two of vpn continue to be negotiated using the crypto map configuration?
The only difference is when i disable this command i need to allow this traffic in outside interface too, right?
The only thing disabling this default setting of "sysopt connection permit-vpn" does is that any traffic coming through a VPN connection doesnt get a free pass through the "outside" interface ACL. It doesnt have effect on the actual VPN negotiation.
Want to clarify a funny thing.
Due to some requirement, i had to configure Remote VPN on LAN Interface of Cisco ASA with in office.
so now when i connect VPN ( that is enabled on LAN interface High security Zone ), i was able to access my Low Seurity zone DMZ, Even if i had ACL on out direction on DMZ interface that was denying the traffic.
means my ACL has no effect, so when i disabled sysopt command then my ACL started blocking traffic and become in action. so its not about on which interface crypto is applied.
in my case even if crypto applied on LAN Side, and traffic wanted to go out to DMZ( Less secure ) Even then ACL was not triggering.
Its called real world functionality :D