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
smc-http678812.2Web browsingBuilt-inAs neededSMC Networks device performing HTTP requests
smc-https678912.2Web browsingBuilt-inAs neededSMC Networks device performing HTTPS requests
hnmp679012.2UnknownBuilt-inAs neededhnmp operates on port 6790 and enables device polling or telemetry in Host Network Management Protocol systems.
hnm679112.2UnknownBuilt-inAs neededhnm operates on port 6791 and supports Host Network Management for secure access and monitoring services.
acnet680112.2UnknownBuilt-inAs neededacnet operates on port 6801 and supports communication in the Accelerator Control Network used in scientific research facilities.
pentbox-sim681712.2UnknownBuilt-inAs neededpentbox-sim operates on port 6817 and facilitates Pentbox Simulation for security testing or simulation tools.
ambit-lm683112.2UnknownBuilt-inAs neededAmbit License Manager protocol for managing software licensing.
netmo-default684112.2UnknownBuilt-inAs needednetmo-default operates on port 6841 and handles default communication for Netmo monitoring or device control systems.
netmo-http684212.2Web browsingBuilt-inAs neededNetwork monitoring tool performing HTTP request
iccrushmore685012.2UnknownBuilt-inAs needediccrushmore operates on port 6850 and refers to experimental or proprietary control services in ICC Rushmore networks.
acctopus-cc686812.2UnknownBuilt-inAs neededacctopus-cc operates on port 6868 and supports control center communication in Acctopus cloud or edge computing platforms.
acctopus-st686812.2UnknownBuilt-inAs neededacctopus-st operates on port 6868 and is used for secure telemetry in Acctopus systems for smart infrastructure.
muse688812.2UnknownBuilt-inAs neededmuse operates on port 6888 and handles multimedia streaming in the Muse audio/video platform.
jetstream690112.2UnknownBuilt-inAs neededjetstream operates on port 6901 and enables high-performance streaming and control in JetStream delivery systems.
ethoscan693512.2UnknownBuilt-inAs neededethoscan operates on port 6935 and is used by Ethoscan services for Ethernet-based scanning or diagnostics.
xsmsvc693612.2UnknownBuilt-inAs neededxsmsvc operates on port 6936 and supports messaging or status services in XSM-based service architectures.
bioserver694612.2UnknownBuilt-inAs neededBioServer protocol used for bioinformatics or lab device communication.
otlp695112.2UnknownBuilt-inAs neededotlp operates on port 6951 and supports OpenTelemetry Protocol for transmitting observability data like traces and metrics.
jmact3696112.2UnknownBuilt-inAs neededjmact3 operates on port 6961 and supports management or communication in JMACT3 control systems.
jmevt2696212.2UnknownBuilt-inAs neededjmevt2 operates on port 6962 and supports event communication and status updates in JM event processing systems.

Was this information helpful?