List of protocols
- Built-in protocols — updated along with the SSG software version. Installing a new version requires a DPI reboot, which causes traffic interruption.
If needed, they can be supplemented with up-to-date attributes from the VAS Cloud. This is only necessary for complex protocols, but the option is available for all. - Cloud protocols created by VAS Experts — are periodically updated from the VAS Cloud. This ensures that popular applications remain up-to-date as their behavior changes. Description
- Custom (user-defined) protocols — protocols created by users via the GUI using VAS Cloud tools. These have higher priority than those loaded from the VAS Cloud, and within them, IP:PORT takes precedence over IP and CIDR. It is possible to add a protocol based on IP, SNI, or AS. Guide.
- DSL protocols — protocols described in the DSL language and connected to DPI as a separate module, without reinstalling the software or causing traffic interruption. Unlike custom protocols, a DSL protocol is a finite state machine that analyzes the first N packets of a flow against defined conditions (ports, AS numbers, payload bytes, DSL expressions) and determines whether the flow matches the protocol.
DSL protocols are created by VAS Experts specialists upon client request to Technical Support.
| Protocol | ID | DPI version | Protocol group | Protocol type | Update | Description |
|---|---|---|---|---|---|---|
| med-ovw | 24004 | 12.2 | Unknown | Built-in | As needed | med-ovw operates on port 24004 and manages overview and status updates in medical system dashboards. |
| med-ci | 24005 | 12.2 | Unknown | Built-in | As needed | med-ci operates on port 24005 and enables clinical interface services in integrated medical information systems. |
| med-net-svc | 24006 | 12.2 | Unknown | Built-in | As needed | med-net-svc operates on port 24006 and supports secure network services in medical environments. |
| filesphere | 24242 | 12.2 | Unknown | Built-in | As needed | filesphere operates on port 24242 and supports Filesphere for distributed file sharing or storage. |
| vista-4gl | 24249 | 12.2 | Unknown | Built-in | As needed | vista-4gl uses port 24249. No additional documentation found. |
| ild | 24321 | 12.2 | Unknown | Built-in | As needed | ild operates on port 24321 and enables remote device management in ILD-controlled environments. |
| hid | 24322 | 12.2 | Unknown | Built-in | As needed | hid operates on port 24322 and facilitates device-level communication with Human Interface Devices over IP. |
| intel_rci | 24386 | 12.2 | Unknown | Built-in | As needed | intel_rci operates on port 24386 and supports command and telemetry for Intel RCI control platforms. |
| tonidods | 24465 | 12.2 | Unknown | Built-in | As needed | tonidods operates on port 24465 and is used by Tonido for device server communication, enabling remote access and file sharing. |
| binkp | 24554 | 12.2 | Unknown | Built-in | As needed | BinkP protocol used in FidoNet message transfer over TCP/IP networks. |
| canditv | 24676 | 12.2 | Unknown | Built-in | As needed | canditv operates on port 24676 and is used for interactive television data communication in CandiTV systems. |
| flashfiler | 24677 | 12.2 | Unknown | Built-in | As needed | flashfiler operates on port 24677 and supports database communication in Borland FlashFiler DBMS. |
| proactivate | 24678 | 12.2 | Unknown | Built-in | As needed | proactivate operates on port 24678 and facilitates ProActivate for software or device activation services. |
| tcc-http | 24680 | 12.2 | Web browsing | Built-in | As needed | a tool or script performing HTTP requests, potentially related to telecommunications carrier control. |
| cslg | 24754 | 12.2 | Unknown | Built-in | As needed | cslg operates on port 24754 and supports communication in CSLG monitoring systems. |
| assoc-disc | 24850 | 12.2 | Unknown | Built-in | As needed | Device association discovery protocol, used in IoT or peripheral pairing systems. |
| find | 24922 | 12.2 | Unknown | Built-in | As needed | find operates on port 24922 and enables service discovery and location-based search in distributed networks. |
| icl-twobase1 | 25000 | 12.2 | Unknown | Built-in | As needed | icl-twobase1 operates on port 25000 and supports communication in ICL TwoBase database or application server cluster. |
| icl-twobase2 | 25001 | 12.2 | Unknown | Built-in | As needed | icl-twobase2 operates on port 25001 and enables failover or secondary services in ICL TwoBase systems. |
| icl-twobase3 | 25002 | 12.2 | Unknown | Built-in | As needed | icl-twobase3 operates on port 25002 and supports communication in ICL TwoBase clustered environments for redundancy and load balancing. |
Was this information helpful?
