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
spramsd577012.2UnknownBuilt-inAs neededspramsd operates on port 5770 and handles secure data communication or control signaling within SPRAM-based systems.
netagent577112.2UnknownBuilt-inAs needednetagent operates on port 5771 and supports monitoring or automation agents in NetAgent-managed systems.
dali-port577712.2UnknownBuilt-inAs neededdali-port operates on port 5777 and supports the DALI (Digital Addressable Lighting Interface) protocol for lighting control and automation.
vts-rpc578012.2UnknownBuilt-inAs neededvts-rpc operates on port 5780 and is part of an RPC-based service for virtual transport or traffic simulation systems
3par-evts578112.2UnknownBuilt-inAs neededHPE 3PAR event service protocol used in enterprise storage systems.
3par-mgmt578212.2UnknownBuilt-inAs neededHPE 3PAR management protocol for storage administration.
3par-mgmt-ssl578312.2UnknownBuilt-inAs neededSecure version of HPE 3PAR management protocol over SSL.
ibar578412.2UnknownBuilt-inAs neededibar operates on port 5784 and supports messaging or remote control features in IBAR automation or telemetry platforms.
3par-rcopy578512.2UnknownBuilt-inAs needed3par-rcopy operates on port 5785 and is used by HPE 3PAR Remote Copy for storage replication between arrays.
cisco-redu578612.2UnknownBuilt-inAs neededCisco redundancy protocol for failover and high availability in network devices.
waascluster578712.2UnknownBuilt-inAs neededwaascluster operates on port 5787 and is used by Cisco WAAS (Wide Area Application Services) for clustering and service coordination.
xtreamx579312.2UnknownBuilt-inAs neededxtreamx operates on port 5793 and supports media streaming or control communication for XtreamX media delivery platforms.
spdp579412.2UnknownBuilt-inAs neededspdp operates on port 5794 and is used by the Simple Peer Discovery Protocol for locating devices in distributed networks.
icmpd581312.2Network servicesBuilt-inAs neededA protocol for ICMPD (ICMP Daemon), serving ICMP-related functions.
spt-automation581412.2UnknownBuilt-inAs neededspt-automation operates on port 5814 and supports communication with SPT Automation systems for industrial or building control environments.
reversion584212.2UnknownBuilt-inAs neededreversion operates on port 5842 and provides version control and synchronization services in revision management tools.
wherehoo585912.2UnknownBuilt-inAs neededwherehoo uses port 5859. No additional documentation found.
ppsuitemsg586312.2UnknownBuilt-inAs neededppsuitemsg operates on port 5863 and facilitates PPSuite Messaging for messaging within the PPSuite environment.
diameters586812.2UnknownBuilt-inAs neededdiameters operates on port 5868 and supports secure Diameter protocol communications in AAA frameworks.
jute588312.2UnknownBuilt-inAs neededjute operates on port 5883 and supports internal communication in Apache ZooKeeper-based distributed systems.

Was this information helpful?