KB ID 0001042 Dtd 08/03/15
I’ve been working on a large firewall deployment for a client, each of their DMZ’s have both a production and a management network. nothing particularly strange about that, but each of their DMZ’s has its own firewalled management network and it’s routable from the LAN.
So If I’m an admin and I want to talk to a Linux appliance in their DMZ via its management interface, my traffic leaves the LAN through the management firewall, but the appliance sees my source IP as being on the LAN, and routes the traffic back to me via the clients production firewall.
Now the simplest way to fix it would be to put a static route on the appliance to route my traffic back via the management firewall, which is fine, BUT what if that appliance is the proxy server? Now I can administer it, but I cant get on the Internet!
Note: I’m NOT performing NAT anywhere in this scenario!
The problem with that is it will translate all traffic from my laptop’s subnet going into this DMZ and I might not want to do that.
Solution Pre ASA 8.3
Solution Post 8.3
To do the same now the syntax is a little different. To demonstrate I have built a small lab in GNS3 to demonstrate. If I want the internal host to talk to the DMZ host, I want the traffic when it gets there to ‘appear’ to have come from 192.168.131.1
To NAT this traffic use the following commands;
object network obj-Host host 126.96.36.199 ! object network obj-DMZ host 192.168.131.10 nat (inside,DMZ) source static obj-Host interface destination static obj-DMZ obj-DMZ
For the Entire Subnet
object network obj-Host-LAN subnet 188.8.131.52 255.255.255.0 ! object network obj-DMZ-LAN host 192.168.131.10 nat (inside,DMZ) source dynamic obj-Host-LAN interface destination static obj-DMZ obj-DMZ
Now if we repeat the process, and ping the DMZ host.
Now when I capture the traffic, the source IP has changed accordingly.
Related Articles, References, Credits, or External Links