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
pegasus927812.2UnknownBuilt-inAs neededpegasus operates on port 9278 and facilitates Pegasus for network management or monitoring services.
pegasus-ctl927912.2UnknownBuilt-inAs neededpegasus-ctl operates on port 9279 and supports Pegasus Control for managing Pegasus system operations.
pgps928012.2UnknownBuilt-inAs neededpgps operates on port 9280 and supports PGPS for secure communication, possibly related to PGP systems.
swtp-port1928112.2UnknownBuilt-inAs neededswtp-port1 operates on port 9281 and supports primary communication for Secure Web Transfer Protocol (SWTP)-enabled applications.
swtp-port2928212.2UnknownBuilt-inAs neededswtp-port2 operates on port 9282 and supports secondary port communication for Secure Web Transfer Protocol (SWTP) systems.
callwaveiam928312.2UnknownBuilt-inAs neededcallwaveiam operates on port 9283 and is used by CallWave for internet-based voicemail or messaging alerts.
visd928412.2UnknownBuilt-inAs neededvisd operates on port 9284 and supports visual display services or diagnostics in enterprise visualization systems.
n2h2server928512.2UnknownBuilt-inAs neededn2h2server operates on port 9285 and supports content filtering services using N2H2 technology.
n2receive928612.2UnknownBuilt-inAs neededn2receive operates on port 9286 and is used for receiving data in N2 protocol-based communication systems.
cumulus928712.2UnknownBuilt-inAs neededcumulus and cumulus-admin operate on ports 9287 and 8954 and manage data transfer and admin interfaces for Cumulus content management platforms.
armtechdaemon929212.2UnknownBuilt-inAs neededarmtechdaemon operates on port 9292 and enables remote access and control for ARMTech hardware or secure embedded platforms.
storview929312.2UnknownBuilt-inAs neededstorview operates on port 9293 and provides management access to storage systems via the StorView interface.
armcenterhttp929412.2Web browsingBuilt-inAs neededARMCenter http Service, registered 2006-04
armcenterhttps929512.2Web browsingBuilt-inAs neededARMCenter https Service, registered 2006-04
vrace930012.2UnknownBuilt-inAs neededvrace uses port 9300. No additional documentation found.
sphinxql930612.2UnknownBuilt-inAs neededsphinxql operates on port 9306 and enables SQL-like querying for the Sphinx full-text search engine.
sphinxapi931212.2UnknownBuilt-inAs neededsphinxapi operates on port 9312 and supports native API communication with the Sphinx search engine.
secure-ts931812.2UnknownBuilt-inAs neededsecure-ts operates on port 9318 and supports Secure Transport Service for encrypted data transport.
guibase932112.2UnknownBuilt-inAs neededguibase operates on port 9321 and supports GUI communication in systems managing enterprise infrastructure or applications.
mpidcmgr934312.2UnknownBuilt-inAs neededmpidcmgr operates on port 9343 and provides manager-level communication for MPIDC data collection and diagnostics.

Was this information helpful?