Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ASA 5520 inside interface used for Clients Default Gateway

I'm having issues when I point my clients DHCP lease gatway to the inside addr of the ASA ( they can not connect to any internal network the ASA has routes too. I validated from the ASA inside addr can see these networks "ping" and he recieves replies... So, I'm thinking the ASA is trying to nat the internal source ADDR when the source conects to him " internal side of the Asa" for the route next hop.

5 REPLIES

Re: ASA 5520 inside interface used for Clients Default Gateway

Hello Scott,

Try this

access-list inside_nat0_outbound permit ip insidenetwork insidenetmask routednetworks routednetmask

nat (inside) 0 access-list inside_nat0_outbound

Also make sure your access-list applied to inside interface does not block traffic.

Regards

New Member

Re: ASA 5520 inside interface used for Clients Default Gateway

Thanks for the info.. One question.. with the NAT (inside) 0 on the inside interface I think it will blow away all my normal inside to outside traffic..?

Re: ASA 5520 inside interface used for Clients Default Gateway

The commadn will effect only the traffic between networks specified in access list. For example, your inside network is 192.168.1.0/24, and you have an internal network routed via ASA 172.16.10.0/24. If you type the following,

access-list inside_nat0_outbound permit ip 192.168.1.0 255.255.255.0 172.16.10.0 255.255.255.0

nat (inside) 0 access-list inside_nat0_outbound

Traffic between these networks wont be NATed bidirectionally, so hosts on these network will be able to connect each other on their actual IPs. But traffic from 192.168.1.0 to any other destination, for example a host in internet 65.125.142.78, this traffic will be natted and connection will be successful.

New Member

Re: ASA 5520 inside interface used for Clients Default Gateway

i'm not really sure how your internal routing is setup but keep id mind that it does not support asymmetrical routing.

so, if packet flow is as follows, pc1-asa-router-pc2, then return trip pc2-router-pc1 (because pc1 and router lan on same subnet), then it will fail. bi-directional traffic must flow through the asa.

http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094e8a.shtml

Note: ASA/PIX does not support ICMP redirects, because it does not support asymmetric routing.

Re: ASA 5520 inside interface used for Clients Default Gateway

You need to couple hussein's commands with the following and it will work:

same-security-traffic permit intra-interface

Have a look at this link:

http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080734db7.shtml

Regards

Farrukh

172
Views
0
Helpful
5
Replies