17. Application Control for Security, HA and QoS
ChiefNET has an integrated Application Control mechanism wherein one can define a list of domains into applications.
The applications are all predefined in a default set. Custom applications may be added for an organization.
For each device, the application can be configured in a Traffic Policy/Traffic Engineering rule.
17.1 Configuring Application Control
To configure the applications, navigate to "Settings" and then to "Application Domains". Here the list of configured applications may be seen. Existing application domains may be edited or new applications may be added.
After verifying that the application is configured, proceed to a device and configure the appropriate Traffic Engineering policies.
Choose the application as the destination and proceed to configure the overall policy-rule (ACCEPT or DENY). Thereafter, proceed to configure the HA and QoS behavior for that application.
- choose an overall policy whether to accept or deny the application from your enterprise.
-
If 'DENY' is chosen as the overall policy, all traffic to that application will be discarded. If the traffic is to be accepted, proceed to configure additional policies for that traffic.
-
failover/load-balancing for that application
- specific threholds for each WAN interface on packet loss/delay/latency parameters specific to that application
- QoS profile for that application for each WAN port
The integrated Application Control mechanism is extremely powerful and flexible at the same time. ChiefNET comes preconfigured with a large number of well-known applications. Our typical customer bases uses it to drop traffic to unwanted domains as well as to offer specific QoS behavior as noted above.
17.2 ChiefNET as DNS Server
In order for Application Control to work, all DNS must be performed by the ChiefNET CPE. If any device or application on premises uses a DNS server and bypasses ChiefNET CPE, Application Control policies will not work.
The customer must ensure that, by policy, the devices within their organization do not use any DNS servers other than ChiefNET CPE's IP.
ChiefNET also automatically forwards/traps the DNS requests on some well-known protocols and ports. However, additional custom rules may be necessary if any device uses unknown DNS servers or DNS-over-HTTPS.