12.03.2015 Views

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Virtual IPs<br />

Firewall Virtual IP<br />

The packets sent from the client <strong>com</strong>puter have a source IP of 192.168.37.55 and<br />

a destination IP of 192.168.37.4. The <strong>FortiGate</strong> unit receives these packets at its<br />

external interface. The virtual IP settings indicate a mapping from 192.168.37.4 to<br />

10.10.10.42 so the packets’ addresses are changed. The source address is<br />

changed to 10.10.10.2 and the destination is changed to 10.10.10.42. The<br />

<strong>FortiGate</strong> unit makes a note of this translation in the firewall session table it<br />

maintains internally. The packets are then sent on their way and arrive at the<br />

server <strong>com</strong>puter.<br />

Figure 192:Example of packet address remapping during NAT from client to server.<br />

Note that the client <strong>com</strong>puter’s address does not appear in the packets the server<br />

receives. After the <strong>FortiGate</strong> unit translates the network addresses, there is no<br />

reference to the client <strong>com</strong>puter’s network. The server has no indication another<br />

network exists. As far as the server can tell, all the <strong>com</strong>munication is <strong>com</strong>ing<br />

directly from the <strong>FortiGate</strong> unit.<br />

When the server answers the client <strong>com</strong>puter, the procedure works the same way<br />

but in the other direction. The server sends its response packets having a source<br />

IP address of 10.10.10.42 and a destination IP address of 10.10.10.2. The<br />

<strong>FortiGate</strong> unit receives these packets at its internal interface. This time however,<br />

the firewall session table entry is used to determine what the destination address<br />

will be translated to.<br />

In this example, the source address is changed to 192.168.37.4 and the<br />

destination is changed to 192.168.37.55. The packets are then sent on their way<br />

and arrive at the client <strong>com</strong>puter.<br />

The server <strong>com</strong>puter’s address does not appear in the packets the client receives.<br />

After the <strong>FortiGate</strong> unit translates the network addresses, there is no reference to<br />

the server <strong>com</strong>puter’s network. The client has no indication the server’s private<br />

network exists. As far as the client is concerned, the <strong>FortiGate</strong> unit is the web<br />

server.<br />

Figure 193:Example of packet address remapping during NAT from server to client.<br />

Note: Virtual IPs are not available or required in transparent mode.<br />

A Virtual IP can be a single IP address or an IP address range bound to a<br />

<strong>FortiGate</strong> unit interface. When you bind an IP address or IP address range to a<br />

<strong>FortiGate</strong> unit interface using a virtual IP, the interface responds to ARP requests<br />

for the bound IP address or IP address range.<br />

<strong>FortiGate</strong> Version 3.0 MR5 <strong>Administration</strong> <strong>Guide</strong><br />

306 01-30005-0203-20070830

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!