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
vscp959812.2UnknownBuilt-inAs neededvscp operates on port 9598 and is used by the Very Simple Control Protocol for automation and control in embedded systems.
robix959912.2UnknownBuilt-inAs neededrobix operates on port 9599 and supports communication with Robix automation or robotic systems.
micromuse-ncpw960012.2UnknownBuilt-inAs neededmicromuse-ncpw operates on port 9600 and supports polling and reporting for Micromuse Netcool platforms.
streamcomm-ds961212.2UnknownBuilt-inAs neededstreamcomm-ds operates on port 9612 and supports directory services in StreamComm platforms for media and communication applications.
iadt-tls961412.2UnknownBuilt-inAs needediadt-tls operates on port 9614 and supports secure transport for IADT protocols in identity or access platforms.
erunbook_agent961612.2UnknownBuilt-inAs needederunbook_agent operates on port 9616 and facilitates eRunbook Agent for automated task execution in runbook systems.
erunbook_server961712.2UnknownBuilt-inAs needederunbook_server operates on port 9617 and supports eRunbook Server for managing runbook automation processes.
condor961812.2UnknownBuilt-inAs neededcondor operates on port 9618 and is used by Condor for distributed computing and job scheduling in Condor systems.
uniport962912.2UnknownBuilt-inAs neededuniport operates on port 9629 and is associated with unified port management systems or software-defined networking interfaces, facilitating streamlined connectivity
peoctlr963012.2UnknownBuilt-inAs neededpeoctlr operates on port 9630 and is used by PEO Controller for process execution orchestration control.
peocoll963112.2UnknownBuilt-inAs neededpeocoll operates on port 9631 and supports PEO Collector for collecting process execution data.
mc-comm963212.2UnknownBuilt-inAs neededmc-comm operates on port 9632 and supports interprocess communication in MC (Management Console) based tools.
pqsflows964012.2UnknownBuilt-inAs neededpqsflows operates on port 9640 and is used by PQS Flows for managing flow-based data processing.
xmms2966712.2UnknownBuilt-inAs neededxmms2 operates on port 9667 and provides audio streaming and control services for the XMMS2 music player daemon.
tec5-sdctp966812.2UnknownBuilt-inAs neededtec5-sdctp operates on port 9668 and is used by TEC5 devices for secure device control and telemetry processing.
client-wakeup969412.2UnknownBuilt-inAs neededClient Wakeup protocol used in Wake-on-LAN or remote desktop management systems.
ccnx969512.2UnknownBuilt-inAs neededccnx operates on port 9695 and is used by Content-Centric Networking (CCNx) protocols for named data object communication.
board-roar970012.2UnknownBuilt-inAs neededboard-roar operates on port 9700 and provides communication for soundboard control or audio event notification systems.
l5nas-parchan974712.2UnknownBuilt-inAs neededl5nas-parchan operates on port 9747 and provides parallel channel communication for L5NAS storage systems.
board-voip975012.2UnknownBuilt-inAs neededBoard VoIP protocol used in digital conferencing and integrated audio systems.

Was this information helpful?