Web caching WAN optimization and web caching
FortiGate Version 4.0 Administration Guide
614 01-400-89802-20090424
http://docs.fortinet.com/ • Feedback
Figure 409: Adding web caching to a passive WAN optimization rule
To configure the server (passive) FortiGate unit
1 Go to WAN Opt. & Cache > Peer and enter a Local Host ID for the server FortiGate
unit.
2 Select Create New and add a Peer Host ID and the IP address for the client side
FortiGate unit.
3 Go to WAN Opt. & Cache > Rule and select Create New.
4 Configure the rule.
5 Select OK to save the rule.
The rule is added to the bottom of the WAN optimization list.
6 If required, move the rule to a different position in the list.
See “Moving a rule to a different position in the rule list” on page 607.
Configuring peer to peer web caching
In a peer to peer web caching configuration you create a peer-to-peer WAN optimization
rule on the client side FortiGate unit and include the peer host ID of the server side
FortiGate unit. In the rule you set Auto-Detect to Off and select Enable Web Cache. Using
this rule, the client side FortiGate unit can create a WAN optimization tunnel only with the
peer that is added to the rule.
In a peer-to-peer configuration you do not have to add a rule to the server side FortiGate
unit. If the server side FortiGate unit peer list contains the client FortiGate unit, the server
FortiGate unit accepts WAN optimization tunnel connections from the client FortiGate unit
and the two units can form a WAN optimization tunnel. The server side FortiGate unit uses
the settings in the rule added to the client side FortiGate unit.
Local Host ID Server_Side
Peer Host ID Client_Side
IP Address 172.10.10.1
Mode Full Optimization
Source 172.20.120.0
Destination 192.168.10.0
Port 1-65535
Auto-Detect Passive
Enable Web Cache Enable
To Next Page
Loading...