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.
- 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.
| Protocol | ID | DPI version | Protocol group | Protocol type | Update | Description |
|---|---|---|---|---|---|---|
| ttl-publisher | 5462 | 12.2 | Tunneling, secure, ssl, pki | Built-in | As needed | TTL-Publisher is a secure telemetry feed for Time-To-Live status or network metrics. |
| ttlpriceproxy | 5463 | 12.2 | Tunneling, secure, ssl, pki | Built-in | As needed | TTLPriceProxy supports encrypted financial pricing feeds in algorithmic trading networks. |
| quailnet | 5464 | 12.2 | Network services | Built-in | As needed | QuailNet control and sync protocol for wireless sensor and metering networks. |
| netops-broker | 5465 | 12.2 | Transactions, banking, trading | Built-in | As needed | NetOps-Broker manages secure connections between financial platforms for real-time transaction coordination. |
| fcp-addr-srvr1 | 5500 | 12.2 | Unknown | Built-in | As needed | fcp-addr-srvr1 operates on port 5500 and is used by FCP Address Server 1 for address management in FCP systems. |
| fcp-addr-srvr2 | 5501 | 12.2 | Unknown | Built-in | As needed | fcp-addr-srvr2 operates on port 5501 and supports FCP Address Server 2 for additional address management. |
| fcp-srvr-inst1 | 5502 | 12.2 | Unknown | Built-in | As needed | fcp-srvr-inst1 operates on port 5502 and supports FCP Server Instance 1 for server instance management. |
| 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). |
Was this information helpful?