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
mbus4700012.2UnknownBuilt-inAs neededmbus operates on port 47000 and enables lightweight message bus communication in embedded or smart device systems.
winrm4700112.2UnknownBuilt-inAs neededwinrm operates on port 47001 and is used by Windows Remote Management (WinRM) for remote administration over the WS-Management protocol.
jvl-mactalk4710012.2UnknownBuilt-inAs neededjvl-mactalk operates on port 47100 and enables communication between MAC-based JVL industrial controllers.
dbbrowse4755712.2Data basesBuilt-inAs neededDBBrowse protocol provides secure search and access to database schemas or indexed datasets.
directplaysrvr4762412.2UnknownBuilt-inAs neededdirectplaysrvr operates on port 47624 and enables session coordination for DirectPlay-based multiplayer games.
ap4780612.2UnknownBuilt-inAs neededAP protocol may refer to Application Proxy in enterprise firewalls or access control.
bacnet4780812.2UnknownBuilt-inAs neededBACnet protocol used in building automation systems for HVAC, lighting, and access control.
nimcontroller4800012.2UnknownBuilt-inAs needednimcontroller operates on port 48000 and provides core control services for NIM infrastructure orchestration.
nimspooler4800112.2UnknownBuilt-inAs needednimspooler operates on port 48001 and manages print and job spooling in NIM (Network Installation Manager) systems.
nimhub4800212.2UnknownBuilt-inAs needednimhub operates on port 48002 and serves as a central communication hub in IBM NIM environments.
nimgtw4800312.2UnknownBuilt-inAs needednimgtw operates on port 48003 and enables gateway functionality for remote deployment in NIM systems.
nimbusdb4800412.2Data basesBuilt-inAs neededNimbusDB protocol manages access to distributed, versioned, and encrypted data services.
nimbusdbctrl4800512.2Data basesBuilt-inAs neededNimbusDBCtrl is a control plane protocol for secure NimbusDB multi-model databases.
3gpp-cbsp4804912.2UnknownBuilt-inAs needed3GPP Cell Broadcast Service Protocol used for emergency alerts in mobile networks.
isnetserv4812812.2UnknownBuilt-inAs neededisnetserv operates on port 48128 and supports infrastructure network services in ISNET platforms.
blp54812912.2UnknownBuilt-inAs neededblp5 operates on port 48129 and supports Bloomberg data services, particularly for enhanced real-time market data feeds.
com-bardac-dw4855612.2UnknownBuilt-inAs neededcom-bardac-dw operates on port 48556 and is used by Bardac Drives for device communication in industrial automation networks.
iqobject4861912.2UnknownBuilt-inAs needediqobject operates on port 48619 and enables communication with IQObject data systems for analytics or telemetry.
matahari4900012.2UnknownBuilt-inAs neededmatahari operates on port 49000 and is used in Matahari infrastructure for agent-based system monitoring and control.
DirectDownloadLink4915212.2UnknownBuilt-inAs neededdirectdownloadlink operates on port 49152 and facilitates direct HTTP-based file transfers between clients.

Was this information helpful?