Fireware includes support for NAT loopback. NAT loopback allows a user on the trusted or optional networks to get access to a public server that is on the same physical Firebox interface by its public IP address or domain name. For NAT loopback connections, the Firebox changes the source IP address of the connection to the IP address of the internal Firebox interface (the primary IP address for the interface that the client and server both use to connect to the Firebox).
To understand how to configure NAT loopback when you use static NAT, we give this example:
Company ABC has an HTTP server on the Firebox trusted interface. The company uses a static NAT rule to map the public IP address to the internal server. The company wants to allow users on the trusted and optional networks to use the public IP address or domain name to get access to this public server.
For this example we assume:
In this example, to allow users on your trusted and optional networks to use the public IP address or domain name to access a public server that is on the trusted network, you must add an HTTP policy that could look like this:
To create this policy:
For more information about how to configure static NAT, see About static NAT.
If you use 1-to-1 NAT to route traffic to servers inside your network, see NAT loopback and 1-to-1 NAT.