Showing results for 
Search instead for 
Did you mean: 
Joe Carey

Cisco ASA static routing to Cisco 831. help with ACL maybe?

Hi all,


What should be a simple task is proving to be difficult and I really need some help.


The Cisco ASA is obviously not a strong point on mine and could do with a point in the right direction. Hopefully this will allow me to learn more about the ASA 5505.



Ok so I have an ASA 5505. Vlan 1 is and VLAN 2 is DHCP from my cable modem.

I have a cisco 831 Ethernet router which will sit between my main LAN and my test LAN which I am setting up for multicast. the Cisco 831 has Ethernet 1 as and the Ethernet 0 is


On the ASA I have an inside route of

On the Cisco 831 there is a route of I can pass traffic through the Cisco 831 to the ASA 5505 and out to the internet, I can ping for example and access everything on my main lan, but the other wan from any host inside the ASA 5505 is unable to ping anything on 10.1.1.x.

Where am I going wrong? I made all my access of my ASA any any, but still it is unable to do anything.

I will attached my configs here with the passwords removed and would appreciate a good kick in the right direction. No doubt this is something simple that I am missing and I am sure it is with the ACL on the ASA 5505 as the packet tracer says the packet is dropped because of the ACL


Thanks. :)




Accepted Solutions

So, on ASA, all the traffic between these two LANs will traverse on the same interface.
Then please add this command in the global config on ASA:
same-security-traffic permit intra-interface

View solution in original post

TTL Exceeded means you have a loop.

The ASA routes 10/8 to the router, but the router has no idea of this range, so chooses the default route which points to the ASA.

This is a loop.

I see that the e0 on the router is connected to Maybe the interface is down? Because the route doesn't show up in "show ip route" on the router.

View solution in original post

Dennis Mink

your interface vlan 2 has no ip address configured on it, so the ASA is not in the transit path between the two VLANS. correct this first.

Please remember to rate useful posts, by clicking on the stars below.

this is not the issue. VLAN 2 goes out to my ISP and my internet is up and working.


When I do a sh ip address I can clearly see that vlan 2 has the external IP assigned to it from my ISP.


The issues is internally from VLAN1 routing to 10.1.1.x.


As I said, the Cisco 831 and anything attached to it can access anything on 192.168.254.x and beyond out to the internet. the problem is I can access anything from 192.168.254.x to 10.1.1.x.

There are no issues between vlan 1 and vlan 2 on the ASA. VLAN 1 is inside and vlan 2 is outside on the ASA only. My issue is between the ASA and the Cisco 831.


ISP-----ASA on VLAN 2 (nat outside) ----ASA Vlan 1 (nat inside) That is all good.


ASA (inside) static route (ip on eth 1 on C831)

Cisco 831 has a static route of (vlan 1 of the ASA)


Traffic on the C831 on 10.1.1.x can pass through the asa out to the internet, but anything on my main lan 192.168.254.x is unable to access anything on 10.1.1.x.


Does that make sense?


What would be the gateway for your hosts in each LAN?

Could you post a topology, and also describe the desired traffic flow from a host in 10.1.1.x and a host int 192.168.254.x ?


I hope this is clear enough.

So, on ASA, all the traffic between these two LANs will traverse on the same interface.
Then please add this command in the global config on ASA:
same-security-traffic permit intra-interface

All this has presented me with was ttl expired in transit :( I cannot see why that is because all static routes are correct, the metric is good so there should be no issues and the 10.1.1.x range can access the internet and main lan.


I did noticed that there was a typo in my static route which has been corrected and my metric is set to 2 so there the TTL is ok.

the C831 can access the main lan and internet without issues but anything on my main lan cannot access the C831 address or anything on the 10 range.


I don't see a route for on the ASA. There's only a host route for

Try this:

no route inside 2
route inside

That was the error that I said I resolved. it was a type.