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
iec-104-sec1999812.2UnknownBuilt-inAs needediec-104-sec operates on port 19998 and provides secure SCADA communication via the IEC 60870-5-104 standard.
dnp-sec1999912.2UnknownBuilt-inAs neededdnp-sec operates on port 19999 and provides encrypted communication for the DNP3 protocol used in SCADA systems.
dnp2000012.2UnknownBuilt-inAs neededdnp operates on port 20000 and enables communication in Distributed Network Protocol 3 for SCADA and automation.
microsan2000112.2UnknownBuilt-inAs neededmicrosan operates on port 20001 and enables storage networking and management for MicroSAN platforms.
commtact-http2000212.2Web browsingBuilt-inAs neededCommtact HTTP, registered 2004-12
commtact-https2000312.2Web browsingBuilt-inAs neededCommtact HTTPS, registered 2004-12
openwebnet2000512.2Network servicesBuilt-inAs neededOpenWebNet is a home automation protocol from BTicino for secure lighting and appliance control.
ss-idi-disc2001212.2UnknownBuilt-inAs neededss-idi-disc operates on port 20012 and is used for discovery or negotiation processes in secure subsystem interfaces.
ss-idi2001312.2UnknownBuilt-inAs neededss-idi operates on port 20013 and is used for communication within secure subsystem interfaces, supporting data exchange in specialized computing environments
opendeploy2001412.2UnknownBuilt-inAs neededopendeploy operates on port 20014 and enables remote deployment and configuration management in Opendeploy platforms.
nburn_id2003412.2UnknownBuilt-inAs needednburn_id operates on port 20034 and supports identification services in NBURN software or backup solutions.
tmophl7mts2004612.2UnknownBuilt-inAs neededtmophl7mts operates on port 20046 and supports HL7 messaging transfer services in T-Mobile healthcare data platforms.
mountd2004812.2UnknownBuilt-inAs neededmountd operates on port 20048 and handles NFS mount requests, enabling client access to remote file systems.
nfsrdma2004912.2UnknownBuilt-inAs needednfsrdma operates on port 20049 and allows NFS to use RDMA (Remote Direct Memory Access) for high-speed file transfers.
tolfab2016712.2UnknownBuilt-inAs neededtolfab uses port 20167. No additional documentation found.
ipdtp-port2020212.2UnknownBuilt-inAs neededipdtp-port operates on port 20202 and supports IPD Transport Protocol communication for data movement across networks.
ipulse-ics2022212.2UnknownBuilt-inAs neededipulse-ics operates on port 20222 and supports communication in iPulse Industrial Control Systems.
emwavemsg2048012.2UnknownBuilt-inAs neededemwavemsg operates on port 20480 and facilitates EMWave Messaging for electromagnetic wave-based communication systems.
track2067012.2UnknownBuilt-inAs neededtrack operates on port 20670 and is used in asset or vehicle tracking systems for transmitting telemetry data.
athand-mmp2099912.2UnknownBuilt-inAs neededathand-mmp operates on port 20999 and provides communication for atHand Mobile Messaging Platform services.

Was this information helpful?