You need to make sure that the ASA, the DHCP clients are sitting behind, has the outside IP permitted in the crypto ACL and the ASA the DHCP server is sitting behind has that IP permitted as the destination. E.g. :
ASA1 (DHCP clients are sitting behind this ASA) :
Public IP : 184.108.40.206
Private network : 192.168.1.0 255.255.255.0
ASA2 (DHCP server is sitting behind this ASA) :
Public IP : 220.127.116.11
Private network : 192.168.2.0 255.255.255.0
DHCP server : 192.168.2.5
Crypto ACL on the ASA1 :
access-list to_main permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0
access-list to_main permit ip host 18.104.22.168 192.168.2.0 255.255.255.0
Crypto ACL on ASA2 :
access-list to_remote permit ip 192.168.2.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list to_remote permit ip 192.168.2.0 255.255.255.0 host 22.214.171.124
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...