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
netserialext31636712.2UnknownBuilt-inAs needednetserialext3 operates on port 16367 and enables extended serial-over-IP communication for legacy device support.
netserialext41636812.2UnknownBuilt-inAs needednetserialext4 operates on port 16368 and allows serial data exchange over IP for device communication in industrial systems.
connected1638412.2UnknownBuilt-inAs neededconnected operates on port 16384 and is used by Connected services for establishing network connections or synchronization.
xoms1661912.2UnknownBuilt-inAs neededxoms operates on port 16619 and is used for exchanging operational messages in enterprise monitoring or automation systems.
vtp1666612.2UnknownBuilt-inAs neededvtp operates on port 16666 and is used for VLAN Trunking Protocol communications, enabling the propagation of VLAN configurations across switches
newbay-snc-mc1690012.2UnknownBuilt-inAs needednewbay-snc-mc operates on port 16900 and is used by NewBay platforms for service network controller management.
sgcip1695012.2UnknownBuilt-inAs neededsgcip operates on port 16950 and facilitates SGCIP (Smart Grid Control IP) for smart grid communication.
intel-rci-mp1699112.2UnknownBuilt-inAs neededintel-rci-mp operates on port 16991 and provides management plane communication for Intel RCI-enabled devices.
amt-redir-tcp1699412.2UnknownBuilt-inAs neededIntel AMT redirection over TCP, part of remote out-of-band management.
amt-redir-tls1699512.2UnknownBuilt-inAs neededIntel AMT redirection over TLS for secure remote system management.
isode-dua1700712.2UnknownBuilt-inAs neededisode-dua operates on port 17007 and enables access to the Directory User Agent in ISODE X.500 directory systems.
soundsvirtual1718512.2UnknownBuilt-inAs neededsoundsvirtual operates on port 17185 and supports virtual sound processing or audio streaming services.
chipper1721912.2UnknownBuilt-inAs neededChipper protocol used for lightweight encrypted tunneling or secure messaging.
avdecc1722112.2UnknownBuilt-inAs neededavdecc operates on port 17221 and supports the Audio Video Discovery, Enumeration, Connection, and Control protocol for networked AV device management.
cpsp1722212.2UnknownBuilt-inAs neededcpsp operates on port 17222 and supports Control Plane Service Protocol for advanced control plane operations.
integrius-stp1723412.2UnknownBuilt-inAs neededintegrius-stp operates on port 17234 and enables Secure Transfer Protocol communication in Integrius platforms.
ssh-mgmt1723512.2UnknownBuilt-inAs neededssh-mgmt operates on port 17235 and is used for secure shell-based remote management tasks across devices and systems
ea1772912.2UnknownBuilt-inAs neededea operates on port 17729 and is used by EA (Enterprise Application) for enterprise-level app communication.
zep1775412.2UnknownBuilt-inAs neededzep operates on port 17754 and is used for transmitting compressed sensor data in ZigBee environments, typically in wireless sensor networks.
zigbee-ip1775512.2UnknownBuilt-inAs neededzigbee-ip operates on port 17755 and supports IPv6 communication over IEEE 802.15.4-based ZigBee networks.

Was this information helpful?