About TCP, SCPS, and SkipWare : About single-ended connection rules
  
About single-ended connection rules
Enable Single-Ended Connection Rules Table
Activates or deactivates all rules in the Single-Ended Interception (SEI) rules table. By default, it is disabled. When disabled, you can still add, move, or remove rules, but they won't take effect until the table is enabled.
The appliance uses the rules to determine whether to enable or pass through SCPS connections. When receiving an SCPS connection on the WAN, the appliance only evaluates the SEI rules table. To pass through an SCPS connection, we recommend setting both an in-path rule and a single-ended connection rule.
Two default rules appear in the list. Both bypass acceleration and pass through matched connections. The first rule matches connections destined to ports listed in the Interactive port label. The second matches connections destined to ports listed in the RBT-Proto port label.
You can also enforce rate pacing for SEI connections where no peer appliance or SCPS device is involved, and SCPS is not negotiated. To enforce rate pacing for a connection, create a rule enabling TCP proxy, select a congestion method for the rule, and then configure a QoS rule (with the same client/server subnet) to use MX-TCP. The appliance then accelerates WAN or LAN-originated proxied connections using MX-TCP.
About TCP, SCPS, and SkipWare
About SCPS connections
About single-ended connection rule settings