Exinda EXNV-10063, Руководство администратора, Страница: 305 / 623

Exinda Network Orchestrator 3 Using | 305
2.
Enter the
Filter Rules
. Similar to other policy configurations, you can specify VLAN, Host/Direction/Host, ToS/DSCP, or
Application. However, the only allowable applications are HTTP, HTTP-ALT, and HTTPS.
To learn more about common use cases for redirecting HTTP traffic, such as, redirecting unauthenticated users to a login
page of your captive portal, see
Integrating Exinda with your Captive Portal
, or such as, redirecting users who have
exceeded their data usage quota, see Quota Enforcement Scenarios .
Related Topics
Configuring a policy to accelerate traffic
Configuring a policy to shape bandwidth
Configuring a policy to discard (block) traffic
Configuring a policy to redirect HTTP traffic to an HTTP Response object webpage
Configuring a policy to mark packets
Reading and writing ToS and DiffServ packet marks
Exinda Appliances can read and write ToS/DSCP marks in packets, allowing fine-grained control and classification of
applications that are marked with Tos/DSCP values as well as applying marking policies to ensure traffic is treated
appropriately by onward network equipment.
Used in conjunction with Exinda classification techniques, including advanced layer 7 detection, users have complete
control over how traffic is marked and subsequently treated in the WAN cloud.
Related topics
How ToS and DiffServ Work
The ToS/DiffServ Field
How ToS and DiffServ work
The ToS (type of service) or DiffServ (differentiated services) field in the IPv4 header, and the Traffic Class field in the IPv6
header are industry standard fields used to classify IP packets so that routers can make QoS (quality of service) decisions
about what path packets should traverse across the network.
Exinda Appliances can read and write ToS/DSCP marks in packets, allowing users fine-grained control and classification
of applications that are marked with ToS/DSCP values as well as applying marking policies to ensure traffic is treated
appropriately by onward network equipment. For example, users may want to ensure that VoIP uses high quality, low
latency (and expensive) links, or, they might want to ensure email or recreational traffic uses cheaper (but less reliable)
links.
Used in conjunction with the Exinda classification techniques, including advanced layer 7 detection, users have
complete control over how traffic is marked, and subsequently treated in the WAN cloud.
Previously, there were 5 different categories that users could use to classify their traffic with the IP ToS field (see RFC 791 ):
Normal Service, Minimize Cost, Maximize Reliability, Maximize Throughput, and Minimize Delay.
These have since been replaced by a new set of values called DSCP (DiffServ Code Points, see RFC 2474). A DSCP is a 6-
bit number; therefore, there are 64 possible DSCP combinations, of which, only a portion have been standardized. IPv6
contains an 8 bit Traffic Class field. The 6 most significant bits are treated the same as IPv4 DSCP. The least 2 significant
bits are not modified by the appliance.
All Exinda products can read and write the ToS/DiffServ field, allowing users to: