Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:dpi:dpi_components:dpiui:user_guide:vas_cloud_services:vascloud_protocol_module [2026/01/27 14:45] – created elena.krasnobryzh | en:dpi:dpi_components:dpiui:user_guide:vas_cloud_services:vascloud_protocol_module [2026/01/27 14:47] (current) – [1. Functions of the protocol module] elena.krasnobryzh | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| - Storage of protocol databases of all operators for which there is customization (cloud + customy protocols). | - Storage of protocol databases of all operators for which there is customization (cloud + customy protocols). | ||
| - Updating protocol databases on DPI operators through the Protocol Download Service. | - Updating protocol databases on DPI operators through the Protocol Download Service. | ||
| - | {{ : | + | {{ : |
| ===== 2. Cloud protocols ===== | ===== 2. Cloud protocols ===== | ||
| Line 14: | Line 14: | ||
| ===== 3. Custom protocols ===== | ===== 3. Custom protocols ===== | ||
| Custom protocols are created by the client’s administrator or VAS Experts engineers in agreement with the client in the client’s GUI. With the help of custom protocols, flexibility, | Custom protocols are created by the client’s administrator or VAS Experts engineers in agreement with the client in the client’s GUI. With the help of custom protocols, flexibility, | ||
| - | Custom protocol is currently defined by IP+port (CIDR), SNI and ASN. The architecture of SSG DPI allows you to supplement these parameters at the request of the customer. [[en: | + | Custom protocol is currently defined by IP+port (CIDR), SNI and ASN. The architecture of SSG DPI allows you to supplement these parameters at the request of the customer. [[en: |
| When creating custom protocols, the Protocol Base for this operator is allocated to a separate storage, since the creation of custom protocols can affect the composition of cloud protocols for correct operation. | When creating custom protocols, the Protocol Base for this operator is allocated to a separate storage, since the creation of custom protocols can affect the composition of cloud protocols for correct operation. | ||
| ==== 3.1. Important features of custom protocols ==== | ==== 3.1. Important features of custom protocols ==== | ||
| - Custom protocol takes precedence over other protocol types. | - Custom protocol takes precedence over other protocol types. | ||
| - | - When you add a list of resources for the custom protocol on the VAS Cloud side, the availability of these resources in existing protocols is checked. In the presence of intersections, | + | - When you add a list of resources for the custom protocol on the VAS Cloud side, the availability of these resources in existing protocols is checked. In the presence of intersections, |
| - The creation time of the custom protocol on the DPI after sending from the GUI is about **15 minutes**, readiness can be tracked by process statuses (see [[en: | - The creation time of the custom protocol on the DPI after sending from the GUI is about **15 minutes**, readiness can be tracked by process statuses (see [[en: | ||
| - By preparing a new protocol tree for the client, a customized version of cloud protocols is created, the resources of which are transferred to custom protocols. | - By preparing a new protocol tree for the client, a customized version of cloud protocols is created, the resources of which are transferred to custom protocols. | ||