69
the best value for most cases. The larger the persistence timeout value, the less chance the
user connection will get sent to a different server. Keep in mind that by keeping a lot of
connections in the WebMux memory, the maximum number of available connections for new
clients will drop. Also, a large persistence timeout will cause uneven load balancing if the
majority of the clients are returning clients.
UDP/NTP Time Server
The WebMux can sync its internal clock with any UDP NTP server. By default it points to a
tier 2 NTP server. You can also set it to your Internet NTP server, or wipe out the entry to
not sync to any NTP server.
Reset Stranded TCP Connections
When a server fails to function, there could be many TCP connections on the WebMux that
are still in the TCP_WAIT state.
If this is 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 c
onnections. The default setting is “YES” to conserve resources.
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 (the masquerade IP).
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 One-Armed DSR Mode.
Insert
“X-Forwarded-For” (SNAT only!)
When SNAT is enabled for a farm, the WebMux will substitute its own IP address as the
originating source.
When you enable this option, an “X-Forwarded-For” MIME header will be
inserted to the HTTP requests that w
ill contain the original requesting client’s IP address.
You can use this information for your server logging or if your application server requires it.
Routing Table
You can add static routes to the WebMux using the Web GUI or through the Command Line
Interface (CLI). From the Web GUI menu,
expand the “network” section and click on “routing table”.
You should see this screen:
