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.
- 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.
| Protocol | ID | DPI version | Protocol group | Protocol type | Update | Description |
|---|---|---|---|---|---|---|
| pago-services2 | 30002 | 12.2 | Unknown | Built-in | As needed | pago-services2 operates on port 30002 and supports online payment service communication in Pago service platforms. |
| kingdomsonline | 30260 | 12.2 | Unknown | Built-in | As needed | kingdomsonline operates on port 30260 and enables multiplayer and backend game services for Kingdoms Online. |
| ovobs | 30999 | 12.2 | Unknown | Built-in | As needed | ovobs operates on port 30999 and is used by OpenView for observer process communication in system monitoring. |
| autotrac-acp | 31020 | 12.2 | Unknown | Built-in | As needed | autotrac-acp operates on port 31020 and supports Autotrac ACP 245 for real-time vehicle tracking and fleet management communication. |
| yawn | 31029 | 12.2 | Unknown | Built-in | As needed | yawn operates on port 31029 and handles notification or alert signals in lightweight or experimental network stacks. |
| xqosd | 31416 | 12.2 | Unknown | Built-in | As needed | xqosd operates on port 31416 and manages QoS (Quality of Service) settings in experimental or extended networking platforms. |
| tetrinet | 31457 | 12.2 | Unknown | Built-in | As needed | tetrinet uses port 31457. No additional documentation found. |
| lm-mon | 31620 | 12.2 | Unknown | Built-in | As needed | lm-mon operates on port 31620 and facilitates License Manager Monitor for monitoring license usage. |
| gamesmith-port | 31765 | 12.2 | Unknown | Built-in | As needed | gamesmith-port operates on port 31765 and enables game development or multiplayer communication in GameSmith tools. |
| iceedcp_tx | 31948 | 12.2 | Unknown | Built-in | As needed | iceedcp_tx operates on port 31948 and manages encrypted data control transmission in ICEEDCP-secured networks. |
| iceedcp_rx | 31949 | 12.2 | Unknown | Built-in | As needed | iceedcp_rx operates on port 31949 and handles encrypted data control reception in ICEEDCP-based secure environments. |
| iracinghelper | 32034 | 12.2 | Unknown | Built-in | As needed | iracinghelper operates on port 32034 and provides telemetry and session coordination for iRacing simulator environments. |
| t1distproc60 | 32249 | 12.2 | Unknown | Built-in | As needed | t1distproc60 operates on port 32249 and supports distributed processing for T1-based data systems in telecom environments. |
| apm-link | 32483 | 12.2 | Unknown | Built-in | As needed | apm-link operates on port 32483 and supports link monitoring and performance tracking in APM (Application Performance Management) tools. |
| sec-ntb-clnt | 32635 | 12.2 | Unknown | Built-in | As needed | sec-ntb-clnt operates on port 32635 and supports Secure NTB Client for secure network terminal bridge communication. |
| DMExpress | 32636 | 12.2 | Unknown | Built-in | As needed | dmexpress operates on port 32636 and facilitates data processing and job execution in DMExpress ETL tools. |
| filenet-powsrm | 32767 | 12.2 | Unknown | Built-in | As needed | filenet-powsrm operates on port 32767 and supports FileNet Power SRM for storage resource management. |
| filenet-tms | 32768 | 12.2 | Unknown | Built-in | As needed | filenet-tms operates on port 32768 and is used by FileNet TMS for task management services in FileNet systems. |
| filenet-rpc | 32769 | 12.2 | Unknown | Built-in | As needed | filenet-rpc operates on port 32769 and is used by FileNet RPC for remote procedure calls in FileNet environments. |
| filenet-nch | 32770 | 12.2 | Unknown | Built-in | As needed | filenet-nch operates on port 32770 and supports FileNet NCH for network channel communication in FileNet systems. |
Was this information helpful?