CLI: TCP Acceleration

You can use the acceleration tcp command configure TCP acceleration settings.

Configuring TCP Acceleration

acceleration tcp {cc|discovery|dual-bridge-bypass|keep-alive|transport|window-scale}

[no] acceleration tcp {discovery|dual-bridge-bypass|keep-alive}

To set the WAN side congestion control algorithm:

acceleration tcp cc {cubic|hybla|highspeed|veno|reno|bic|vegas|htcp|yeah|illinois|scalable|lp|westwood}

To enable appliance auto-discovery:

[no] acceleration tcp discovery

To enable accelerated traffic to be processed on only one bridge:

[no] acceleration tcp dual-bridge-bypass

When enabled, acceleration will be processed on only one bridge, which is good for backhauled settings. Default is enabled.
When disabled, accelerated traffic can be handled on any bridge, which is good for aggregated link settings with asymmetric routes.

To manage keep-alive settings:

[no] acceleration tcp keep-alive {enable|timeout}

enable - Enables the sending of keep-alive packets on the WAN. The timeout specifies when to activate the keep-alives if enabled.
timeout - Specifies the amount of time, in seconds, that a connection may be idle before sending keep-alive packets is enabled. Keep-alive packets are sent once per minute until either a response is received, or 5 minutes passes. If five minutes passes without a response the connection is terminated.

To set the transport mode:

acceleration tcp transport {transparent|tunnelled}

To set the window scaling factor, which determines how large the TCP window is allowed to grow per connection:

acceleration tcp window-scale <factor>

<factor> - 0 - 14. The default is 5, which equates to a TCP window of 2MB. Increasing one step in the factor doubles the TCP window size.
0 - 64k
1 - 128k
2 - 256k
3 - 512k
4 - 1M
5 - 2M
6 - 4M
7 - 8M
8 - 16M
9 - 32M
10 - 64M
11 - 128M
12 - 256M
13 - 512M
14 - 1G