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

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.
  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.
ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
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.
snip-slave3365612.2UnknownBuilt-inAs neededsnip-slave operates on port 33656 and supports SNIP Slave for secondary network interface protocol operations.
turbonote-23424912.2UnknownBuilt-inAs neededturbonote-2 operates on port 34249 and provides secondary communication support for TurboNote tools and services.
p-net-local3437812.2UnknownBuilt-inAs neededp-net-local operates on port 34378 and provides local network communication for P-NET fieldbus systems in industrial automation.
dhanalakshmi3456712.2UnknownBuilt-inAs neededdhanalakshmi operates on port 34567 and supports services in custom or regional enterprise networks.
profinet-rt3496212.2UnknownBuilt-inAs neededprofinet-rt operates on port 34962 and supports PROFINET Real-Time for real-time industrial network communication.
profinet-rtm3496312.2UnknownBuilt-inAs neededprofinet-rtm operates on port 34963 and supports PROFINET Real-Time Multicast for multicast industrial communication.
profinet-cm3496412.2UnknownBuilt-inAs neededprofinet-cm operates on port 34964 and facilitates PROFINET Context Manager for managing industrial device contexts.

Was this information helpful?