Configuration Mode Commands : Client Accelerator commands : policy id in-path rule pass-through
  
policy id in-path rule pass-through
Adds a pass-through in-path rule on the specified policy. Allows the SYN packet to pass through the SteelHead Mobile unoptimized.
Syntax
[no] policy id <id> in-path rule pass-through [srcaddr <subnet>] [dstaddr <subnet> dstport <port>] [dst-host <host‑label>] [cloud-accel <mode>] [rulenum <rule-number>] [description <description>]
Parameters
<id>
Policy ID number.
srcaddr <subnet>
Specifies the source subnet for this rule: for example, 1.2.3.4/32
dstaddr <subnet>
dstport <port>
Specifies the destination subnet and port.
For the subnet address, use the format XXX.XXX.XXX.XXX/XX.
For the port, you can specify a single port (number), a port label, or all to specify all ports.
dst-host <host‑label>
Specifies a destination host label for this rule. You configure the host label settings using the host-label command.
A destination IP address and host label cannot be specified in the same rule. A host label can be used instead of a destination IP address.
Enter an empty string, represented by two quotation marks (""), to remove a host label.
cloud-accel <mode>
Applies only if you have subscribed to a Software as a Service (SaaS) platform.
Specifies a cloud-acceleration action mode for this rule.
After you subscribe to a SaaS platform and enable it, ensure that cloud acceleration is ready and enabled. If cloud acceleration is enabled, then, by default, connections to the subscribed SaaS platform will be optimized by the SteelHead SaaS. You do not need to add an in-path rule unless you want to optimize specific users and not others. Specify one of these modes:
• auto - If the in-path rule matches, the connection is optimized by the Riverbed SteelHead Cloud Accelerator (SCA) connection.
• passthru - If the in-path rule matches, the connection is not optimized by the SteelHead SaaS, but it follows the rule’s other parameters so that the connection might be optimized by this SteelHead with other SteelHeads in the network, or it might be passed through.
Domain labels and cloud acceleration are mutually exclusive except when the _cloud-accel-saas host label is used. To use cloud acceleration with domain labels, we recommend placing the domain label rules lower than cloud acceleration rules in your rule list so the cloud rules match before the domain label rules.
rulenum <rule-number>
Specifies the order in which the rule is consulted: 1-N or start or end.
The rule is inserted into the list at the specified position. For example, if you specify rulenum as 3, the new rule will be 3, the old rule 3 becomes 4, and subsequent rules also move down the list.
Specify start for the rule to be the first rule and end for the rule to be the last rule.
If you do not specify a rule number, the rule is added to the end of the list.
description <description>
Specifies a description of the rule.
Usage
The SteelHead Mobile automatically intercepts traffic on all IP addresses (0.0.0.0) and ports (all) and optimizes according to default settings.
Specify pass-through rules for traffic that you want to pass through to its destination without optimization by the Riverbed system.
No optimization is performed on the TCP connection initiated by this SYN packet. You define pass-through rules to exclude subnets from optimization. Traffic is also passed through when the SteelHead Mobile is in bypass mode. (Pass through of traffic might occur because of in-path rules or because the connection was established before the SteelHead Mobile was put in place or before the SteelHead Mobile service was enabled.)
The no command option disables the rule. The no command option has the following syntax: no in-path rule <rulenum>.
For detailed information about in-path rules, see the SteelHead User Guide.
Example
amnesiac (config) # in-path rule pass-through srcaddr 10.10.10.1 rulenum 25
Product
Client Accelerator
Related Commands
show policy id