User guide

- 43 -
Reset Stranded TCP Connections:
When a server failed to function, there could be many TCP connections still in TCP_WAIT
state. If this set to “Yes,” when client tries to access the failed server, the WebMux will
pretend the server is sending TCP Reset to the client, thus freeing all the TCP_WAIT state
connections. Default setting is “Yes” to conserve resources.
Route Returning Layer 4 Load Balanced Traffic Whence Original Client Traffic
Came:
For configurations where you have multiple gateways, your originating connections may
come from the server side. You may have returning connections from the internet side that
you may want to be sure to be routed through the same gateway that the originating server
side client used to reach the destination. Default setting is “Yes”.
Front Proxy Addresses:
By default, the WebMux will use the main IP address you configured in the router/internet
LAN interface or Bridge IP as the source IP for outgoing connections. You may want to
specify a different IP address instead. You can list more than one IP address by separating
them with a colon (:). If you have more than one front proxy address, the WebMux will
choose a proxy address in a round-robin fashion. This option is not available in 1 Arm Out-
of-Path Mode.
SNAT:
By default, the WebMux will not change the source IP address of the originating client from
the internet/router LAN side of the network when sending packets to the destination server.
When the server receives these packets it will see that the client is external from its network.
In some cases, as in OCS 2007R2, you may need to enable SNAT so that the destination
server see that the request is coming from a local client. Enable this option so that the
WebMux will substitute its own IP address as the originating client.
6.3.1 Adding Static Routes
You can add static routes to the WebMux using the Web GUI or through the Command Line
Interface (CLI). From the Web GUI, hover the mouse over the “network” menu, then click
on the “routing table” button.