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
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.
VMTP6510512.2UnknownBuilt-inAs neededvmtp operates on port 65105 and supports the Versatile Message Transaction Protocol for reliable message exchange in distributed systems.
SECURE-VMTP6510612.2UnknownBuilt-inAs neededsecure-vmtp operates on port 65106 and is used by Secure VMTP for secure Versatile Message Transaction Protocol communication.
VINES6510712.2UnknownBuilt-inAs neededvines operates on port 65107 and is associated with Banyan VINES networking, supporting legacy enterprise communication protocols.
TTP6510812.2UnknownBuilt-inAs neededttp operates on port 65108 and refers to a proprietary or internal Transaction Transport Protocol used in secure systems.
NSFNET-IGP6510912.2UnknownBuilt-inAs needednsfnet-igp operates on port 65109 and refers to the Interior Gateway Protocol used in the NSFNET backbone for routing data.
DGP6511012.2UnknownBuilt-inAs neededdgp operates on port 65110 and supports Datagram Delivery Protocol in distributed or real-time systems.
TCF6511112.2UnknownBuilt-inAs neededtcf operates on port 65111 and refers to the Target Communication Framework used in embedded system development for debugging and communication.
EIGRP6511212.2UnknownBuilt-inAs neededeigrp operates on port 65112 and supports Enhanced Interior Gateway Routing Protocol for advanced IP routing.
OSPFIGP6511312.2UnknownBuilt-inAs neededospfigp operates on port 65113 and is a variant of the OSPF Interior Gateway Protocol for routing in advanced networks.
Sprite-RPC6511412.2UnknownBuilt-inAs neededsprite-rpc operates on port 65114 and supports remote procedure calls in the Sprite distributed operating system environment.
LARP6511512.2UnknownBuilt-inAs neededlarp operates on port 65115 and enables local address resolution in specialized LARP (Local ARP) environments.
AX.256511712.2UnknownBuilt-inAs neededax.25 operates on port 65117 and supports packet radio communication using the AX.25 data link layer protocol.
IPIP6511812.2UnknownBuilt-inAs neededipip operates on port 65118 and supports IP encapsulation within IP for tunneling or mobility purposes.
MICP6511912.2UnknownBuilt-inAs neededmicp operates on port 65119 and is used for control plane messaging in Multimedia Internet Conferencing Protocol.
SCC-SP6512012.2UnknownBuilt-inAs neededscc-sp operates on port 65120 and supports secure communications for control protocols in security platforms.
ETHERIP6512112.2UnknownBuilt-inAs neededetherip operates on port 65121 and supports EtherIP for tunneling Ethernet frames over IP networks.
ENCAP6512212.2UnknownBuilt-inAs neededencap operates on port 65122 and facilitates Encapsulation Protocol for encapsulating data in network packets.

Was this information helpful?