Cisco Cisco ASR 5000
ACS Ruledef Configuration Mode Commands
tethering-detection ▀
Command Line Interface Reference, StarOS Release 18 ▄
1175
tethering-detection
This command allows you to define rule expressions to match tethered or non-tethered flows.
Product
ACS
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration > Ruledef Configuration
active-charging service service_name > ruledef ruledef_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-acs-ruledef)#
Syntax
tethering-detection [ ip-ttl | os-ua ] { flow-not-tethered | flow-tethered }
no tethering-detection
no
Deletes the tethering detection configuration from the ruledef.
ip-ttl
Specifies to select flows that were tethered or not tethered as per IP-TTL values.
os-ua
Specifies to select flows that were tethered or not tethered as per OS-UA lookups.
In 18 and later releases, IPv6 OS-based tethering detection is supported.
In 18 and later releases, IPv6 OS-based tethering detection is supported.
flow-not-tethered
Specifies to match if tethering is not detected on flow.
flow-tethered
Specifies to match if tethering is detected on flow.
Usage
Use this command to define rule expressions to match tethered/non-tethered flows.
Note that in order for the rule containing the tethering-detection configuration to get matched, at least one
valid rule line has to be present in it.
This configuration is treated in a special manner by the rule matching engine in that it is excluded from the
condition
Note that in order for the rule containing the tethering-detection configuration to get matched, at least one
valid rule line has to be present in it.
This configuration is treated in a special manner by the rule matching engine in that it is excluded from the
condition
multi-line-or all-lines
. For example, if there are three rule-lines in a ruledef and multi-
line-or is enabled as follows:
ruledef all-tethered-web-traffic