List of protocols [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

List of protocols

  1. 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.
  2. 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
  3. 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.
  4. 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.

ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
apm-link3248312.2UnknownBuilt-inAs neededapm-link operates on port 32483 and supports link monitoring and performance tracking in APM (Application Performance Management) tools.
sec-ntb-clnt3263512.2UnknownBuilt-inAs neededsec-ntb-clnt operates on port 32635 and supports Secure NTB Client for secure network terminal bridge communication.
DMExpress3263612.2UnknownBuilt-inAs neededdmexpress operates on port 32636 and facilitates data processing and job execution in DMExpress ETL tools.
filenet-powsrm3276712.2UnknownBuilt-inAs neededfilenet-powsrm operates on port 32767 and supports FileNet Power SRM for storage resource management.
filenet-tms3276812.2UnknownBuilt-inAs neededfilenet-tms operates on port 32768 and is used by FileNet TMS for task management services in FileNet systems.
filenet-rpc3276912.2UnknownBuilt-inAs neededfilenet-rpc operates on port 32769 and is used by FileNet RPC for remote procedure calls in FileNet environments.
filenet-nch3277012.2UnknownBuilt-inAs neededfilenet-nch operates on port 32770 and supports FileNet NCH for network channel communication in FileNet systems.
filenet-rmi3277112.2UnknownBuilt-inAs neededfilenet-rmi operates on port 32771 and supports FileNet RMI for remote method invocation in FileNet systems.
filenet-pa3277212.2UnknownBuilt-inAs neededfilenet-pa operates on port 32772 and supports FileNet Process Analyzer for process monitoring and analysis.
filenet-cm3277312.2UnknownBuilt-inAs neededfilenet-cm operates on port 32773 and facilitates FileNet Content Manager for enterprise content management.
filenet-re3277412.2UnknownBuilt-inAs neededfilenet-re operates on port 32774 and supports FileNet RE for rules engine communication in FileNet systems.
filenet-pch3277512.2UnknownBuilt-inAs neededfilenet-pch operates on port 32775 and is used by FileNet Process Channel for process data exchange.
filenet-peior3277612.2UnknownBuilt-inAs neededfilenet-peior operates on port 32776 and supports FileNet PEI Orchestration for process execution and integration.
filenet-obrok3277712.2UnknownBuilt-inAs neededfilenet-obrok operates on port 32777 and facilitates FileNet Object Broker for object management in FileNet.
mlsn3280112.2UnknownBuilt-inAs neededmlsn operates on port 32801 and supports MLSN (Multi-Level Secure Network) communications in classified systems.
retp3281112.2UnknownBuilt-inAs neededretp operates on port 32811 and provides transaction processing communication in RETP-based financial applications.
idmgratm3289612.2UnknownBuilt-inAs neededidmgratm operates on port 32896 and handles ATM device identification in integrated identity management systems.
aurora-balaena3312312.2UnknownBuilt-inAs neededaurora-balaena operates on port 33123 and supports communication for Aurora Balaena services, typically in data visualization or monitoring tools.
diamondport3333112.2UnknownBuilt-inAs neededdiamondport operates on port 33331 and provides specialized data exchange in DIAMOND industrial or defense platforms.
dgi-serv3333312.2UnknownBuilt-inAs neededdgi-serv operates on port 33333 and handles services in DGI data gateway environments.

Was this information helpful?