ā02-08-2024 08:46 AM
We have an ASA in AWS and it has 2 VPNs, 1 to AWS (subnet A) and 1 to Azure (Subnet B)
All traffic from the ASA to subnet B is source NAT'ed, so we never have to change or add subnets when going to subnet B.
Subnet Z is on the inside interface of the ASA. Subnet Z to subnet A works and subnet Z to subnet B works.
We are trying to get from Subnet A to subnet B. I have done an outside/outside NAT with the src NAT set as well.
Subnet B is also set as a local network on the ASA to AWS VPN, but if I look at the tunnel details on ASDM when trying to connect from subnet A to subnet B, I dont see the flow being built.
AWS side has routes to subnet B in both the VPC and tunnel and the all the required subnets are covered by the tunnel details on AWS
We do other hairpinning from Anyconnect to subnet A and subnet B, so we know hairpinning is OK in general.
I just can't figure out what is missing to get from subnet A to subnet B
ā02-08-2024 09:22 AM
As I know you already solve this issue yesterday.
This new or update to last issue ?
Thanks
MHM
ā02-09-2024 01:13 AM
This is a different issue
ā02-09-2024 01:43 AM - edited ā02-09-2024 01:44 AM
hope this note help you in your issue
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide