To configure TCP Optimization parameters, go to Configuration->TCPO Settings.

The latency thresholds can be changed in RTTi-small and RTTi-large.

There is also a threshold for access latencies, between the BQN and the end subscribers (RTTa), that could be used if two very different access technologies are present in the traffic (e.g., wireless and fiber) and the metrics need to be separated (normally will remain at 0 ms meaning no small RTTa differentiation).

Latency thresholds affect only to the way the metrics are classified and displayed, not to the TCP optimization, which adjusts continuously to each individual connection characteristics, latencies included.

To disable all TCP optimization in the BQN, regardless of what the flow policy dictates, switch off the toggle Overall TCP Optimization. This is done to temporally disable TCPO while debugging an issue or during maintenance tasks.

If there is a NAT between the BQN and the end users, the Adaptive Initial Window should be off (On by default) ), because the adaptive algorithm that tries to find the best initial window per subscriber is no longer meaningful when a lot of real subscribers sit behind a NAT IP address that the BQN is treating as an individual subscriber.

It is also possible to modify the TCP initial window from its default of 10 packets. Changes to the initial window are only recommended for paths with very high latencies, such as a satellite link.