Trouble getting traffic to pass between multiple VPN tunnels

Posted on 2013-12-17
Last Modified: 2013-12-17
I am having trouble getting traffic to pass between remote VPN endpoints. I am leaning towards this being a NAT issue, but am unsure how to verify or remedy.

I have attached a diagram that lays out a simple topology.

I am sitting on the CO Network ( /24) and need to contact the tower at /22.

I am able to:
-Ping from the CO ASA to (inside interface on Field ASA)
-Ping from (Com Tower Router) to

I cannot ping from the /24 network to, which is what I need.

These tunnels terminate on the "outside" interfaces of the ASA's and all of my NAT exempt statements are applied to "inside" interfaces.

I'm sure configs pieces will be necessary, but I'll leave it at this for now.

Please help!
Question by:enervest
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
LVL 15

Expert Comment

ID: 39724814
What version of the IOS is on the ASA units in question?

Do you have
icmp unreachable rate-limit 1 burst-size 1

Open in new window

in the configuration of the ASAs?

Also, can you perform a NET VIEW to the systems on the network, or some other non-ICMP traffic?

Does the Field Office ASA have access lists configured to allow traffic from the Central Office to traverse to the Com Tower site?

Author Comment

ID: 39724837
Field is 8.25 and CO is 9.13

That command is on each ASA in question.

At this time, there is no other way to perform anything but ICMP tests.

There are ACL's configured for the traffic to pass, for example....this is configured on the Tower Router.
    10 permit ip (30 matches)
LVL 15

Expert Comment

ID: 39724849
And is the reverse ACL on the CO ASA?  Is the ACL traversal rule on the FO ASA?
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.


Author Comment

ID: 39724871
The ACL's are in place and seem to be working.

If I ping from the network, or ping from, I see the session being build on the Field Office ASA, but it doesn't get to the other side, for entry from a ping on to

7      Dec 17 2013      06:45:42                          Built local-host outside:

What do you mean by ACL traversal rule? I do suspect a NAT (or something else?) issue on the Field Office ASA.
LVL 15

Expert Comment

ID: 39724894
There has to be a rule on the FO ASA for the traffic in each direction from the CT router to and from the CO ASA

Have you used the packet-tracer command on the two ASAs to determine at which point in the process the packet traversal is failing?

Author Comment

ID: 39724946
I am in the process of doing so now.

When trying to ping from 10.26.1.X to, would my traffic enter and exit on the outside interface (VPN tunnels) of the Field Office ASA?
LVL 15

Expert Comment

ID: 39724983
Essentially.  The traffic should never hit the inside of the FO ASA.
Have you reviewed

Author Comment

ID: 39725016
Then it appears that's where my issue lies. Packet tracer shows an ICMP hitting an implict deny there, even when I've added an ACL on the outside interface allowing that traffic.

I have reviewed the document and my end to end issue will likely still persist once the ACL piece is resolved. Typically on ASA's, your NAT exempt statements are going to run from inside to outside, right?

In this scenario, I suppose this particular traffic would be "outside to outside", so I would need some NAT exempt rule with the proper source and destination, but I am not sure how I would go about applying that.

Please see the attachment for the packet tracer output and ACL. Packet tracer is saying the trace is denied due to the deny all, just two lines above my configured ACL.

What am I missing here?
LVL 15

Accepted Solution

WalkaboutTigger earned 500 total points
ID: 39725054
I did not see an attachment to your most recent post.

Do you have these global configuration lines on the CO and FO ASAs?

same-security-traffic permit inter-interface
same-security-traffic permit intra-interface

Also, while it is using pre-8.3 configuration examples, look at this configuration example - something similar is likely going to be needed on the FO ASA

Author Comment

ID: 39725473
same-security-traffic permit intra-interface

That ended up being the fix. Found that in a blog online as well which led me to try it, then came back here and saw you suggested it also.

All of my NAT statements and ACL's were good...I was just seeing the traffic drop unexpectedly at the Field Office ASA.

Regardless, thanks for the assistance!

Author Closing Comment

ID: 39725475
same-security-traffic permit intra-interface was the fix!

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Secure VPN Connection terminated locally by the Client.  Reason 442: Failed to enable Virtual Adapter. If you receive this error on Windows 8 or Windows 8.1 while trying to connect with the Cisco VPN Client then the solution is a simple registry f…
I've written this article to illustrate how we can implement a Dynamic Multipoint VPN (DMVPN) with both hub and spokes having a dynamically assigned non-broadcast multiple-access (NBMA) network IP (public IP). Here is the basic setup of DMVPN Pha…
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question