Académique Documents
Professionnel Documents
Culture Documents
Note: If you use URL host rewrite functionality in your policies, mismatches can
occur between the client-provided IP address and the resolved, rewritten
hostname. In these cases, a routing lookup is performed and an interface route,
static route, or default route is used.
106
Chapter 6: Routing on the ProxySG
107
Volume I: Getting Started
Enabling Return-to-Sender
To enable RTS, use the return-to-sender command. For example:
#(config) return-to-sender inbound {disable | enable}
Enables or disables return-to-sender for inbound sessions.
#(config) return-to-sender outbound {disable | enable}
Enables or disables return-to-sender for outbound sessions.
DNS Verification
In transparent deployments, the ProxySG verifies the destination IP addresses
provided by the client. This is known as L2/L3 transparency.
Note: The Trust Destination IP option overrides DNS verification. This option is
recommended for acceleration deployments only. For more information about
this option, see Volume 2: Proxies and Proxy Services.
108
Chapter 6: Routing on the ProxySG
For hostname-less protocols such as CIFS and FTP, the IP address can always be
trusted. For other protocols, such as HTTP, RTSP, and MMS, which have a
hostname that must be resolved, verification can be an issue. URL rewrites that
modify the hostname also can cause verification to fail.
L2/L3 transparency is not supported in explicit proxy deployments, or if the
destination IP addresses cannot be verified by the ProxySG. In these cases, you
must configure static routes to hosts that are only accessible through gateways
other than the default gateway.
Transparent ADN connections that are handed off to an application proxy (HTTP
or MAPI, for example) can utilize L2/L3 transparency. Also, transparent ADN
connections that are tunneled but not handed off can utilize the functionality.
Note: IM is not supported with trust client addressing. To support IM, proper
routes must be configured for Internet access and IM client-to-client
communication.
109