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
metaedit-ws639012.2UnknownBuilt-inAs neededmetaedit-ws operates on port 6390 and enables web service communication for MetaEdit+ modeling tools.
faxcomservice641712.2UnknownBuilt-inAs neededfaxcomservice operates on port 6417 and supports Faxcom Service for fax communication over networks.
syserverremote641812.2Remote controlBuilt-inAs neededRemote server system management.
svdrp641912.2UnknownBuilt-inAs neededsvdrp operates on port 6419 and supports the Simple VDR Protocol for controlling Video Disk Recorder (VDR) systems remotely.
nim-vdrshell642012.2UnknownBuilt-inAs needednim-vdrshell operates on port 6420 and allows shell-level control of VDR (Virtual Data Recovery) components within NIM.
nim-wan642112.2UnknownBuilt-inAs needednim-wan operates on port 6421 and supports wide area deployment coordination in IBM NIM.
pgbouncer643212.2UnknownBuilt-inAs neededpgbouncer operates on port 6432 and supports PgBouncer for PostgreSQL connection pooling and management.
sun-sr-https644312.2Web browsingBuilt-inAs neededKubernetes API server (TCP)
sge_qmaster644412.2UnknownBuilt-inAs neededsge_qmaster operates on port 6444 and is used by SGE Queue Master for managing job queues in Sun Grid Engine.
sge_execd644512.2UnknownBuilt-inAs neededsge_execd operates on port 6445 and supports SGE Execution Daemon for executing jobs in Sun Grid Engine.
mysql-proxy644612.2Tunneling, secure, ssl, pkiBuilt-inAs neededMySQL-Proxy is a middleware tool for inspecting, filtering, and encrypting MySQL client-server traffic.
skip-cert-recv645512.2UnknownBuilt-inAs neededskip-cert-send and skip-cert-recv operate on ports 6455–6456 and manage certificate exchange in SKIP security frameworks.
skip-cert-send645612.2UnknownBuilt-inAs neededskip-cert-send and skip-cert-recv operate on ports 6455–6456 and manage certificate exchange in SKIP security frameworks.
lvision-lm647112.2UnknownBuilt-inAs neededlvision-lm operates on port 6471 and provides license management for L-View Vision or similar software platforms.
sun-sr-http648012.2Web browsingBuilt-inAs neededKubernetes API server (TCP)
servicetags648112.2UnknownBuilt-inAs neededservicetags operates on port 6481 and facilitates Service Tags for identifying and managing service instances.
ldoms-mgmt648212.2UnknownBuilt-inAs neededldoms-mgmt operates on port 6482 and is used by LDOMs Management for managing logical domains in Oracle systems.
SunVTS-RMI648312.2UnknownBuilt-inAs neededsunvts-rmi operates on port 6483 and is used by SunVTS (Sun Validation Test Suite) for remote method invocation in test environments.
sun-sr-jms648412.2UnknownBuilt-inAs neededsun-sr-jms operates on port 6484 and supports Java Messaging Service integration within Sun Service Registry.
sun-sr-iiop648512.2UnknownBuilt-inAs neededsun-sr-iiop operates on port 6485 and supports standard CORBA IIOP protocol messaging in Sun Service Registry.

Was this information helpful?