Re: configuring accesslist in a multisite vpn environment
I would recommend that you control access from remote to HQ via ACL applied on the remote site. Reasons being:
1) Since the traffic will be blocked, it would be good to block it sooner than later to save on bandwith.
2) If traffic is blocked in the HQ, it consumes the resources both on the remote site (ie: traffic being encrypted, sent across the vpn tunnel, and then finally be blocked on the HQ end). While, if you block it on the remote site, the traffic will not even be processed which saves resources along the way).
3) Simpler implementation at the remote end as the ACL will be simpler and it only reflects the remote site access).
However, you can also configure ACL on the HQ site if you wish. Outbound ACL on the HQ inside interfaces can be configured to restrict access, however, please kindly be advised that you would also need to take into consideration all other traffic going outbound through your inside interface (this will include traffic initiated from outside towards inside, other inside interfaces, dmz interfaces, and also all the remote vpn access towards your inside interface).
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...