List of protocols
- 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. - 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
- 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.
- 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.
| Protocol | ID | DPI version | Protocol group | Protocol type | Update | Description |
|---|---|---|---|---|---|---|
| MPEGTS | 49219 | 12.2 | Unknown | Built-in | As needed | mpegts operates on port 49219 and is used for streaming MPEG Transport Stream data over IP, commonly in IPTV services. |
| ZELLO | 49220 | 12.2 | Instant messengers | Built-in | As needed | Zello uses push-to-talk VoIP over encrypted UDP with secure channel sync and presence updates. |
| SSL Unknown | 49221 | 12.2 | Unknown | Built-in | As needed | ssl unknown uses port 49221. No additional documentation found. |
| TELEGRAM | 49224 | 12.2 | Instant messengers | Built-in | As needed | Telegram uses MTProto for encrypted messaging, media sync, and cloud chat history. |
| HOPOPT | 65024 | 12.2 | Unknown | Built-in | As needed | hopopt operates on port 65024 and refers to Hop-by-Hop Options used in IPv6 routing for optional information delivery. |
| ICMP | 65025 | 12.2 | Network services | Built-in | As needed | A protocol for ICMP (Internet Control Message Protocol), managing network control messages. |
| IGMP | 65026 | 12.2 | Unknown | Built-in | As needed | igmp operates on port 65026 and handles Internet Group Management Protocol messages for multicast group membership. |
| GGP | 65027 | 12.2 | Unknown | Built-in | As needed | ggp operates on port 65027 and refers to Gateway-to-Gateway Protocol for routing updates in legacy networks. |
| IPv4-Encap | 65028 | 12.2 | Unknown | Built-in | As needed | ipv4-encap operates on port 65028 and supports encapsulated IPv4 transport, commonly used in tunneling protocols. |
| ST | 65029 | 12.2 | Unknown | Built-in | As needed | st operates on port 65029 and refers to a specialized or internal protocol with limited public documentation. |
| TCP Unknown | 65030 | 12.2 | Unknown | Built-in | As needed | tcp unknown operates on port 65030 and refers to an undocumented or proprietary protocol over TCP with limited public information. |
| IGP | 65033 | 12.2 | Unknown | Built-in | As needed | igp operates on port 65033 and refers to Interior Gateway Protocols used for routing within autonomous systems. |
| BBN-RCC-MON | 65034 | 12.2 | Unknown | Built-in | As needed | bbn-rcc-mon operates on port 65034 and provides remote monitoring capabilities for BBN RCC systems in secure communications. |
| NVP-II | 65035 | 12.2 | Unknown | Built-in | As needed | nvp-ii operates on port 65035 and supports communication in NVP II (Network Voice Protocol) for secure voice transport. |
| PUP | 65036 | 12.2 | Unknown | Built-in | As needed | pup operates on port 65036 and supports PARC Universal Packet for early Xerox networking protocols. |
| ARGUS | 65037 | 12.2 | Unknown | Built-in | As needed | Argus protocol used in network audit and real-time traffic flow monitoring systems. |
| EMCON | 65038 | 12.2 | Unknown | Built-in | As needed | emcon operates on port 65038 and supports EMC Control for enterprise management and control operations. |
| XNET | 65039 | 12.2 | Unknown | Built-in | As needed | xnet operates on port 65039 and refers to internal or cross-platform network messaging systems with limited public specification. |
| CHAOS | 65040 | 12.2 | Unknown | Built-in | As needed | Legacy MIT Chaosnet protocol used for early LAN communication in Lisp systems. |
| UDP Unknown | 65041 | 12.2 | Unknown | Built-in | As needed | udp unknown operates on port 65041 and refers to an undocumented or proprietary UDP-based protocol with limited public information. |
Was this information helpful?
