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
synchronet-db610012.2Data basesBuilt-inAs neededSynchronet-DB is a backend protocol for BBS systems using encrypted user and message storage.
synchronet-rtc610112.2UnknownBuilt-inAs neededsynchronet-rtc operates on port 6101 and manages real-time communication features in Synchronet BBS platforms.
synchronet-upd610212.2UnknownBuilt-inAs neededsynchronet-upd operates on port 6102 and enables update communication for Synchronet BBS systems, supporting version checks and software maintenance.
rets610312.2UnknownBuilt-inAs neededrets operates on port 6103 and supports data exchange in Real Estate Transaction Standard systems.
dbdb610412.2Data basesBuilt-inAs neededDBDB is an internal data bus protocol managing secure routing of SQL tasks and metadata.
primaserver610512.2UnknownBuilt-inAs neededprimaserver operates on port 6105 and facilitates PrimaServer for primary server operations in networked systems.
mpsserver610612.2UnknownBuilt-inAs neededmpsserver operates on port 6106 and enables Media Processing Server control or data handling.
etc-control610712.2UnknownBuilt-inAs neededetc-control operates on port 6107 and supports ETC Control for environmental or equipment control systems.
sercomm-scadmin610812.2UnknownBuilt-inAs neededsercomm-scadmin operates on port 6108 and facilitates Sercomm SCAdmin for administrative control of Sercomm devices.
globecast-id610912.2UnknownBuilt-inAs neededglobecast-id operates on port 6109 and enables authentication and identification for Globecast media distribution platforms.
softcm611012.2UnknownBuilt-inAs neededsoftcm operates on port 6110 and is used for communication with soft controller modules in software-defined industrial systems.
spc611112.2UnknownBuilt-inAs neededspc operates on port 6111 and handles control communication in secure or specialized protocol controllers.
dtspcd611212.2UnknownBuilt-inAs neededdtspcd operates on port 6112 and supports Distributed Time Service Provider Client Daemon for time synchronization.
dayliteserver611312.2UnknownBuilt-inAs neededdayliteserver operates on port 6113 and supports Daylite Server for managing Daylite CRM server operations.
wrspice611412.2UnknownBuilt-inAs neededwrspice operates on port 6114 and supports remote simulation control for the WRspice circuit simulation tool.
xic611512.2UnknownBuilt-inAs neededxic operates on port 6115 and supports data communication in XIC software used for electronic design automation.
xtlserv611612.2UnknownBuilt-inAs neededxtlserv operates on port 6116 and provides translation or transport layer services in extended communication frameworks.
daylitetouch611712.2UnknownBuilt-inAs neededdaylitetouch operates on port 6117 and is used by Daylite Touch for syncing Daylite CRM data on mobile devices.
tipc611812.2UnknownBuilt-inAs neededtipc operates on port 6118 and is used by the Transparent Inter-Process Communication protocol for fast and reliable messaging between nodes in clustered systems.
spdy612112.2UnknownBuilt-inAs neededspdy operates on port 6121 and is a deprecated Google protocol designed to speed up web traffic by multiplexing streams.

Was this information helpful?