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 |
|---|---|---|---|---|---|---|
| fcp-srvr-inst2 | 5503 | 12.2 | Unknown | Built-in | As needed | fcp-srvr-inst2 operates on port 5503 and is used by FCP Server Instance 2 for additional server instances. |
| fcp-cics-gw1 | 5504 | 12.2 | Unknown | Built-in | As needed | fcp-cics-gw1 operates on port 5504 and facilitates FCP CICS Gateway 1 for transaction processing integration. |
| checkoutdb | 5505 | 12.2 | Network services | Built-in | As needed | A protocol for Checkout DB, managing database checkout operations over networks. |
| amc | 5506 | 12.2 | Unknown | Built-in | As needed | AMC protocol for Automated Media Control or network video distribution. |
| sgi-eventmond | 5553 | 12.2 | Unknown | Built-in | As needed | sgi-eventmond operates on port 5553 and supports SGI Event Monitor Daemon for event monitoring in SGI systems. |
| sgi-esphttp | 5554 | 12.2 | Web browsing | Built-in | As needed | SGI ESP HTTP |
| personal-agent | 5555 | 12.2 | Unknown | Built-in | As needed | personal-agent operates on port 5555 and is used by Personal Agent for user-specific assistant or service communication. |
| freeciv | 5556 | 12.2 | Unknown | Built-in | As needed | freeciv operates on port 5556 and enables multiplayer gameplay in the open-source Freeciv strategy game. |
| farenet | 5557 | 12.2 | Unknown | Built-in | As needed | farenet operates on port 5557 and is used by FareNet for fare collection or transportation system networking. |
| westec-connect | 5566 | 12.2 | Unknown | Built-in | As needed | westec-connect uses port 5566. No additional documentation found. |
| enc-eps-mc-sec | 5567 | 12.2 | Unknown | Built-in | As needed | enc-eps-mc-sec operates on port 5567 and supports ENC EPS MC Security for secure multi-channel encryption. |
| sdt | 5568 | 12.2 | Unknown | Built-in | As needed | sdt operates on port 5568 and supports SDT (Service Data Transfer) for transferring service-related data. |
| rdmnet-ctrl | 5569 | 12.2 | Unknown | Built-in | As needed | rdmnet-ctrl operates on port 5569 and is used by RDMnet Control for controlling networked lighting devices (shared with rdmnet-device). |
| rdmnet-device | 5569 | 12.2 | Unknown | Built-in | As needed | rdmnet-device operates on port 5569 and supports RDMnet Device for remote device management in networked lighting (shared with rdmnet-ctrl). |
| sdmmp | 5573 | 12.2 | Unknown | Built-in | As needed | sdmmp operates on port 5573 and supports management and monitoring communication in Secure Device Management Protocol environments. |
| lsi-bobcat | 5574 | 12.2 | Unknown | Built-in | As needed | lsi-bobcat operates on port 5574 and enables system or hardware communication in LSI Bobcat storage platforms. |
| ora-oap | 5575 | 12.2 | Unknown | Built-in | As needed | ora-oap operates on port 5575 and provides Oracle Application Protocol services for database or application access. |
| fdtracks | 5579 | 12.2 | Unknown | Built-in | As needed | fdtracks operates on port 5579 and facilitates FDTracks for file or data tracking services. |
| tmosms0 | 5580 | 12.2 | Unknown | Built-in | As needed | tmosms0 operates on port 5580 and handles signaling for mobile-originated SMS in telecom infrastructure. |
| tmosms1 | 5581 | 12.2 | Unknown | Built-in | As needed | tmosms1 operates on port 5581 and is used in telecom signaling systems for mobile-originated SMS services. |
Was this information helpful?
