List of protocols [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

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. Description
  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.
  4. 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.

ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
clutild717412.2UnknownBuilt-inAs neededclutild operates on port 7174 and supports cluster utility daemon functions in distributed system environments.
fodms720012.2UnknownBuilt-inAs neededfodms operates on port 7200 and provides management and scheduling services in FODMS (Field Operations Data Management System).
dlip720112.2UnknownBuilt-inAs neededdlip operates on port 7201 and supports Device Layer IP communication in embedded or smart devices.
ramp722712.2UnknownBuilt-inAs neededramp operates on port 7227 and supports RAMP (Remote Access Management Protocol) for remote system access.
citrixupp722812.2UnknownBuilt-inAs neededCitrix Universal Print Protocol (UPP) for delivering print jobs to virtual sessions.
citrixuppg722912.2UnknownBuilt-inAs neededCitrix UPP Gateway protocol for managing and routing Citrix print services.
display723612.2UnknownBuilt-inAs neededdisplay operates on port 7236 and supports remote graphical display protocols or services.
pads723712.2UnknownBuilt-inAs neededpads operates on port 7237 and enables data sharing and collaboration in PADS engineering or design environments.
cnap726212.2UnknownBuilt-inAs neededcnap operates on port 7262 and is associated with the Cisco Network Access Protocol for access control and policy enforcement.
watchme-7272727212.2UnknownBuilt-inAs neededwatchme-7272 operates on port 7272 and supports communication for the WatchMe monitoring or remote assistance platform.
oma-rlp727312.2UnknownBuilt-inAs neededoma-rlp operates on port 7273 and supports OMA Radio Link Protocol for messaging between mobile devices and servers.
oma-rlp-s727412.2UnknownBuilt-inAs neededoma-rlp-s operates on port 7274 and provides secure Radio Link Protocol transport for OMA systems.
oma-ulp727512.2UnknownBuilt-inAs neededoma-ulp operates on port 7275 and supports the User Location Protocol in OMA (Open Mobile Alliance) services.
oma-ilp727612.2UnknownBuilt-inAs neededoma-ilp operates on port 7276 and supports Internet Location Protocol communication in OMA-compliant location services.
oma-ilp-s727712.2UnknownBuilt-inAs neededoma-ilp-s operates on port 7277 and provides secure messaging for the OMA Internet Location Protocol.
oma-dcdocbs727812.2UnknownBuilt-inAs neededoma-dcdocbs operates on port 7278 and enables data synchronization and distribution in OMA Dynamic Content Delivery environments.
ctxlic727912.2UnknownBuilt-inAs neededctxlic operates on port 7279 and provides licensing services for Citrix products.
itactionserver1728012.2UnknownBuilt-inAs neededitactionserver1 operates on port 7280 and is used for primary communication in IT Action Server cluster environments.
itactionserver2728112.2UnknownBuilt-inAs neededitactionserver2 operates on port 7281 and handles secondary node communication for IT Action Server clusters.
mzca-action728212.2UnknownBuilt-inAs neededmzca-action operates on port 7282 and facilitates automated responses in MZCA platforms.

Was this information helpful?