Consider the following network.
Things to notice:
Subnets 22.214.171.124/24 and 126.96.36.199/24 are being routed to the outside of the ASA.
There is a static NAT statement in the ASA to translate the real IP 192.168.5.22 to 188.8.131.52
There is a static NAT statement in the ASA to translate the real IP 192.168.5.33 to 184.108.40.206
So how do you get this to work properly?
In ASA pre-8.3 code the ASA would ARP for the static NATs it would have regardless if it’s connected or not.
In ASA 8.3-8.4(4), THIS IS IMPOSSIBLE
In ASA 8.4(5)+ Cisco realized their major mistake and implemented the command:
When else can I use this?
Another scenario to use this is when you have a router with multiple IPs on its interface that is connected to an ASA with a single IP. The ASA won’t accept any packets for the other subnets that the router thinks is connected. By applying this command it will accept packets for the other subnets.
What’s the risk?
By enabling this feature it could facilitate denial of service (DoS) attack against the ASA; a user on any interface could send out many ARP replies and overload the ASA ARP table with false entries. If you enable it be careful of what is physically plugging into the ASA since it can cause this problem.