I am installing 4 ASA 5505's in a hub and spoke topology with a static IP at the hub and dynamic IP's at the spokes.
The first two ASAs are up and it seems to be working but I am not sure if it is configured as well as it should be.
There is a custom group policy and ACL at the hub which is associated with the Tunnel Group and allows me to specify which hosts on the hub network can be reached from the spoke. I also created an additional access list on the inside interface of the hub in order to prevent anyone on the hub network from connecting to hosts on the spoke network. Prior to doing this, anyone on the hub network could connect to anything on the spoke network. I am trying to do most of the config at the hub when possible. Also, In the near future I expect we will require the ability to move traffic between spokes "hairpinning".
Please let me know if the configuration I have described makes sense or if there is a better approach.
Thanks in advance
*The hub site is temporarily DHCP but I used the current IP for testing the tunnel until I get a static IP
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...