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
UTI6514412.2UnknownBuilt-inAs neededuti operates on port 65144 and supports communication for Unified Transport Interface in secure or enterprise-level network environments.
SMP6514512.2UnknownBuilt-inAs neededsmp operates on port 65145 and facilitates Simple Management Protocol for lightweight network management tasks.
SM6514612.2UnknownBuilt-inAs neededsm operates on port 65146 and supports session management services in private enterprise systems.
FIRE6514912.2UnknownBuilt-inAs neededfire operates on port 65149 and refers to a secure or experimental protocol with limited public documentation.
CRTP6515012.2UnknownBuilt-inAs neededcrtp operates on port 65150 and refers to a compressed RTP variant for low-latency media streaming.
CRUDP6515112.2UnknownBuilt-inAs neededcrudp operates on port 65151 and supports compressed UDP messaging in constrained or embedded environments.
SSCOPMCE6515212.2UnknownBuilt-inAs neededsscopmce operates on port 65152 and is associated with Signalling Control protocols, facilitating message exchange in ATM networks.
IPLT6515312.2UnknownBuilt-inAs needediplt operates on port 65153 and refers to IP Load Transport protocol for balancing and redundancy.
SPS6515412.2UnknownBuilt-inAs neededsps operates on port 65154 and supports communication for secure processing systems or specialized protocol services within enterprise or embedded networks.
PIPE6515512.2UnknownBuilt-inAs neededpipe operates on port 65155 and supports PIPE (Protocol Independent Packet Exchange) for flexible packet handling.
SCTP Unknown6515612.2UnknownBuilt-inAs neededsctp unknown operates on port 65156 and refers to an undefined SCTP-based protocol with limited documentation.
FC6515712.2UnknownBuilt-inAs neededfc operates on port 65157 and is used by Fragment Congestion for managing fragmented packet congestion.
RSVP-E2E-IGNORE6515812.2UnknownBuilt-inAs neededrsvp-e2e-ignore and rsvp operate on ports 65070–65158 and provide signaling for reservation of resources in IP networks using the Resource Reservation Protocol.
Mobility6515912.2UnknownBuilt-inAs neededmobility operates on port 65159 and refers to internal or private protocol communications for mobile network functions.
UDPLite6516012.2UnknownBuilt-inAs neededudplite operates on port 65160 and supports UDP-Lite, a lightweight User Datagram Protocol variant for error-tolerant data transmission.
MPLS-in-IP6516112.2UnknownBuilt-inAs neededmpls-in-ip operates on port 65161 and enables MPLS packet tunneling over IP networks for virtual circuit emulation.
HIP6516312.2UnknownBuilt-inAs neededhip operates on port 65163 and refers to the Host Identity Protocol used for secure IP-based communication with identity separation.
Shim66516412.2UnknownBuilt-inAs neededshim6 operates on port 65164 and supports Site Multihoming by IPv6 Intermediation for IPv6 multihoming.
WESP6516512.2UnknownBuilt-inAs neededwesp uses port 65165. No additional documentation found.
ROHC6516612.2UnknownBuilt-inAs neededrohc operates on port 65166 and supports Robust Header Compression for optimized IP traffic.

Was this information helpful?