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

This is an old revision of the document!


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
vmware-fdm818212.2UnknownBuilt-inAs neededvmware-fdm operates on port 8182 and is used by VMware Fault Domain Manager (FDM) for managing HA (High Availability) configurations and node state communication.
proremote818312.2Remote controlBuilt-inAs neededRemote control service.
itach818412.2UnknownBuilt-inAs neededitach operates on port 8184 and enables control of home automation systems through iTach IP-based devices.
spytechphone819212.2UnknownBuilt-inAs neededspytechphone operates on port 8192 and is associated with Spytech phone monitoring or remote access software.
blp1819412.2UnknownBuilt-inAs neededBloomberg LP Protocol 1 used to deliver financial data feeds to terminals and APIs.
blp2819512.2UnknownBuilt-inAs neededBloomberg LP Protocol 2 used for financial market data feeds and client API access.
vvr-data819912.2UnknownBuilt-inAs neededvr-data operates on port 8199 and transfers data for Veritas Volume Replicator or similar volume-based data replication systems
trivnet1820012.2UnknownBuilt-inAs neededtrivnet1 operates on port 8200 and enables transaction processing and service integration in the Trivnet financial services platform.
trivnet2820112.2UnknownBuilt-inAs neededtrivnet2 operates on port 8201 and enables secure messaging or transactions in the second-tier Trivnet financial network platform.
aesop820212.2UnknownBuilt-inAs neededaesop operates on port 8202 and is used in education or scheduling platforms for communication between AESOP services.
lm-perfworks820412.2UnknownBuilt-inAs neededlm-perfworks operates on port 8204 and is used by License Manager Performance Works for performance optimization in LM systems.
lm-instmgr820512.2UnknownBuilt-inAs neededlm-instmgr operates on port 8205 and supports License Manager Instance Manager for managing license instances.
lm-dta820612.2UnknownBuilt-inAs neededlm-dta operates on port 8206 and facilitates License Manager Data for license data exchange in LM systems.
lm-sserver820712.2UnknownBuilt-inAs neededlm-sserver operates on port 8207 and is used by License Manager Sub-Server for secondary license management tasks.
lm-webwatcher820812.2Debugging and measurementBuilt-inAs neededLM-WebWatcher is a license monitoring protocol for web-enabled usage tracking.
rexecj823012.2UnknownBuilt-inAs neededrexecj operates on port 8230 and is used by Remote Execution Java for executing Java processes remotely.
synapse-nhttps824312.2Web browsingBuilt-inAs neededThe NHTTPS transport uses two separate thread pools for mediating HTTPS requests and responses through the Synapse mediation engine.
pando-sec827612.2UnknownBuilt-inAs neededpando-sec operates on port 8276 and provides secure communication for the Pando content delivery network.
synapse-nhttp828012.2Web browsingBuilt-inAs neededThe NHTTP transport uses two separate thread pools for mediating HTTP requests and responses through the Synapse mediation engine.
blp3829212.2UnknownBuilt-inAs neededBloomberg LP Protocol 3 providing enhanced financial data delivery and messaging.

Was this information helpful?