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
IPv6-NoNxt6508312.2UnknownBuilt-inAs neededipv6-nonxt operates on port 65083 and refers to the IPv6 No Next Header extension, used in experimental or restricted transport cases.
IPv6-Opts6508412.2UnknownBuilt-inAs neededipv6-opts operates on port 65084 and handles optional header extension processing in IPv6 packets for advanced routing or QoS.
AnyHIP6508512.2UnknownBuilt-inAs neededAnyHIP associated with Host Identity Protocol for secure mobile networking.
CFTP6508612.2Data transferBuilt-inAs neededCFTP is a compressed file transfer protocol optimized for low-bandwidth encrypted networks.
AnyLN6508712.2UnknownBuilt-inAs neededAnyLN refers to AnyLayer Network protocol in industrial networking.
SAT-EXPAK6508812.2UnknownBuilt-inAs neededsat-expak operates on port 65088 and supports data packaging and transfer in satellite communication networks.
RVD6509012.2UnknownBuilt-inAs neededrvd operates on port 65090 and supports remote virtual desktop connectivity and management.
IPPC6509112.2UnknownBuilt-inAs neededippc operates on port 65091 and supports Industrial Plant Process Control communication in distributed automation systems.
AnyDFS6509212.2UnknownBuilt-inAs neededAnyDFS protocol for distributed file system access or federation.
SAT-MON6509312.2UnknownBuilt-inAs neededsat-mon operates on port 65093 and provides monitoring communication in satellite data platforms.
VISA6509412.2UnknownBuilt-inAs neededvisa operates on port 65094 and refers to internal or proprietary communication for VISA payment or processing networks.
IPCV6509512.2UnknownBuilt-inAs neededipcv operates on port 65095 and supports communication in Inter-Process Communication via Virtualization systems.
CPNX6509612.2UnknownBuilt-inAs neededcpnx operates on port 65096 and supports Control Plane Network Exchange for control plane data sharing.
CPHB6509712.2UnknownBuilt-inAs neededcphb operates on port 65097 and facilitates Control Plane Heartbeat for maintaining control plane connectivity.
WSN6509812.2UnknownBuilt-inAs neededwsn operates on port 65098 and supports communication in wireless sensor networks for telemetry or control.
PVP6509912.2UnknownBuilt-inAs neededpvp operates on port 65099 and is used by PVP (Peer Video Protocol) for peer-to-peer video communication.
BR-SAT-MON6510012.2UnknownBuilt-inAs neededBrazilian Satellite Monitoring protocol used for environmental or telecommunications data.
SUN-ND6510112.2UnknownBuilt-inAs neededsun-nd operates on port 65101 and supports Sun Network Disk services for remote file system access and boot environments.
WB-MON6510212.2UnknownBuilt-inAs neededwb-mon uses port 65102. No additional documentation found.
WB-EXPAK6510312.2UnknownBuilt-inAs neededwb-expak operates on port 65103 and is associated with data packaging or export functions in proprietary systems.