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
lm-sserver820712.2UnknownBuilt-inAs neededlm-sserver operates on port 8207 and is used by License Manager Sub-Server for secondary license management tasks.
rexecj823012.2UnknownBuilt-inAs neededrexecj operates on port 8230 and is used by Remote Execution Java for executing Java processes remotely.
pando-sec827612.2UnknownBuilt-inAs neededpando-sec operates on port 8276 and provides secure communication for the Pando content delivery network.
blp3829212.2UnknownBuilt-inAs neededBloomberg LP Protocol 3 providing enhanced financial data delivery and messaging.
hiperscan-id829312.2UnknownBuilt-inAs neededhiperscan-id operates on port 8293 and enables ID transmission or management in HiperScan systems for high-speed scanning.
blp4829412.2UnknownBuilt-inAs neededblp4 operates on port 8294 and is used by Bloomberg services for real-time financial data and messaging.
tmi830012.2UnknownBuilt-inAs neededtmi operates on port 8300 and supports telemetry messaging and integration for industrial or research-based data collection systems.
amberon830112.2UnknownBuilt-inAs neededAmberon protocol linked to IoT-enabled traffic management systems.
hub-open-net831312.2UnknownBuilt-inAs neededhub-open-net operates on port 8313 and enables node registration and communication in HubOpenNet frameworks.
tnp-discover832012.2UnknownBuilt-inAs neededtnp-discover operates on port 8320 and facilitates discovery of Transparent Network Protocol (TNP) devices on a local network.
tnp832112.2UnknownBuilt-inAs neededtnp operates on port 8321 and is used for Transparent Network Protocol communications, enabling low-latency data transmission.
server-find835112.2UnknownBuilt-inAs neededserver-find operates on port 8351 and is used by Server Find services for locating servers on a network.
cruise-enum837612.2UnknownBuilt-inAs neededcruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms.
cruise-swroute837712.2UnknownBuilt-inAs neededcruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms.
cruise-config837812.2UnknownBuilt-inAs neededcruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms.
cruise-diags837912.2UnknownBuilt-inAs neededcruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms.
cruise-update838012.2UnknownBuilt-inAs neededcruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms.
m2mservices838312.2UnknownBuilt-inAs neededm2mservices operates on port 8383 and supports communication for machine-to-machine (M2M) IoT applications and services.
cvd840012.2UnknownBuilt-inAs neededC Technologies Licensing protocol used for software license validation.
sabarsd840112.2UnknownBuilt-inAs neededsabarsd operates on port 8401 and provides communication services for Sabar Software's remote system diagnostics.

Was this information helpful?