| Protocol | ID | DPI version | Protocol group | Protocol type | Update | Description |
|---|---|---|---|---|---|---|
| lm-instmgr | 8205 | 12.2 | Unknown | Built-in | As needed | lm-instmgr operates on port 8205 and supports License Manager Instance Manager for managing license instances. |
| lm-dta | 8206 | 12.2 | Unknown | Built-in | As needed | lm-dta operates on port 8206 and facilitates License Manager Data for license data exchange in LM systems. |
| lm-sserver | 8207 | 12.2 | Unknown | Built-in | As needed | lm-sserver operates on port 8207 and is used by License Manager Sub-Server for secondary license management tasks. |
| lm-webwatcher | 8208 | 12.2 | Debugging and measurement | Built-in | As needed | LM-WebWatcher is a license monitoring protocol for web-enabled usage tracking. |
| rexecj | 8230 | 12.2 | Unknown | Built-in | As needed | rexecj operates on port 8230 and is used by Remote Execution Java for executing Java processes remotely. |
| synapse-nhttps | 8243 | 12.2 | Web browsing | Built-in | As needed | The NHTTPS transport uses two separate thread pools for mediating HTTPS requests and responses through the Synapse mediation engine. |
| pando-sec | 8276 | 12.2 | Unknown | Built-in | As needed | pando-sec operates on port 8276 and provides secure communication for the Pando content delivery network. |
| synapse-nhttp | 8280 | 12.2 | Web browsing | Built-in | As needed | The NHTTP transport uses two separate thread pools for mediating HTTP requests and responses through the Synapse mediation engine. |
| blp3 | 8292 | 12.2 | Unknown | Built-in | As needed | Bloomberg LP Protocol 3 providing enhanced financial data delivery and messaging. |
| hiperscan-id | 8293 | 12.2 | Unknown | Built-in | As needed | hiperscan-id operates on port 8293 and enables ID transmission or management in HiperScan systems for high-speed scanning. |
| blp4 | 8294 | 12.2 | Unknown | Built-in | As needed | blp4 operates on port 8294 and is used by Bloomberg services for real-time financial data and messaging. |
| tmi | 8300 | 12.2 | Unknown | Built-in | As needed | tmi operates on port 8300 and supports telemetry messaging and integration for industrial or research-based data collection systems. |
| amberon | 8301 | 12.2 | Unknown | Built-in | As needed | Amberon protocol linked to IoT-enabled traffic management systems. |
| hub-open-net | 8313 | 12.2 | Unknown | Built-in | As needed | hub-open-net operates on port 8313 and enables node registration and communication in HubOpenNet frameworks. |
| tnp-discover | 8320 | 12.2 | Unknown | Built-in | As needed | tnp-discover operates on port 8320 and facilitates discovery of Transparent Network Protocol (TNP) devices on a local network. |
| tnp | 8321 | 12.2 | Unknown | Built-in | As needed | tnp operates on port 8321 and is used for Transparent Network Protocol communications, enabling low-latency data transmission. |
| server-find | 8351 | 12.2 | Unknown | Built-in | As needed | server-find operates on port 8351 and is used by Server Find services for locating servers on a network. |
| cruise-enum | 8376 | 12.2 | Unknown | Built-in | As needed | cruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms. |
| cruise-swroute | 8377 | 12.2 | Unknown | Built-in | As needed | cruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms. |
| cruise-config | 8378 | 12.2 | Unknown | Built-in | As needed | cruise-config, cruise-diags, cruise-enum, cruise-swroute, and cruise-update operate on ports 8376–8380 and manage diagnostic, configuration, and update services in Cruise control platforms. |
Описание