subnet side add rule

index {<rule-number> start \| end}>	Specifies a rule number, start, or end. SteelHeads evaluate rules in numerical order starting with rule 1. If the conditions set in the rule match, then the rule is applied, and the system moves on to the next packet. If the conditions set in the rule do not match, the system consults the next rule. For example, if the conditions of rule 1 do not match, rule 2 is consulted. If rule 2 matches the conditions, it is applied, and no further rules are consulted. The type of a matching rule determines which action the SteelHead takes on the connection.
network <network-prefix>	Specifies the source subnet IP address and subnet mask. • For IPv4 addresses, use this format: XXX.XXX.XXX.XXX/<0-32> • For IPv6 addresses, use this format: X:X:X::X/<0-128>
is {lan \| wan}	Specifies whether the addresses on the subnet are on the LAN side or WAN side. In virtual in-path configurations, all traffic is flowing in and out of one physical interface.

Subnet-side rules are used in a virtual in-path deployment to support Flow Export, to support a client-side SteelHead, or to exempt certain subnets from QoS enforcement or path selection. Subnet-side rules let you configure subnets as LAN-side subnets or WAN-side subnets for a virtual in-path SteelHead. The subnet-side rules determine whether traffic originated from the LAN or the WAN-side of the SteelHead based on the source subnet. You must configure subnets on each SteelHead in a virtual in-path configuration, as the subnets for each will likely be unique.