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

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.
  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.
ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
inovaport22300112.2UnknownBuilt-inAs neededinovaport2 operates on port 23001 and enables communication in InovaPort multi-port infrastructure.
inovaport32300212.2UnknownBuilt-inAs neededinovaport3 operates on port 23002 and handles session services in InovaPort systems.
inovaport42300312.2UnknownBuilt-inAs neededinovaport4 operates on port 23003 and provides auxiliary services in InovaPort environments.
inovaport52300412.2UnknownBuilt-inAs neededinovaport5 operates on port 23004 and enables telemetry or media handling in InovaPort architecture.
inovaport62300512.2UnknownBuilt-inAs neededinovaport6 operates on port 23005 and supports monitoring and diagnostics in InovaPort platforms.
gntp2305312.2UnknownBuilt-inAs neededgntp operates on port 23053 and is used by the Growl Notification Transport Protocol for delivering cross-platform notifications.
s1022327212.2UnknownBuilt-inAs neededs102 operates on port 23272 and supports the S102 protocol used in digital TV and satellite communication environments.
elxmgmt2333312.2UnknownBuilt-inAs neededelxmgmt operates on port 23333 and is used by ELX Management for Emulex device management and control.
novar-alarm2340112.2UnknownBuilt-inAs needednovar-alarm operates on port 23401 and supports alarm signaling and management in Novar control systems.
novar-global2340212.2UnknownBuilt-inAs needednovar-global operates on port 23402 and enables global control or configuration communication in Novar building management systems.
aequus2345612.2UnknownBuilt-inAs neededaequus operates on port 23456 and enables communication with Aequus enterprise or financial service platforms.
aequus-alt2345712.2UnknownBuilt-inAs neededaequus-alt operates on port 23457 and provides alternate access to Aequus systems for cloud or data services.
areaguard-neo2354612.2UnknownBuilt-inAs neededJapanese network security platform protocol used for desktop protection.
med-ltp2400012.2UnknownBuilt-inAs neededmed-ltp operates on port 24000 and handles long-term patient data transport in medical applications.
med-fsp-rx2400112.2UnknownBuilt-inAs neededmed-fsp-rx operates on port 24001 and receives streaming medical data in health IT platforms.
med-fsp-tx2400212.2UnknownBuilt-inAs neededmed-fsp-tx operates on port 24002 and manages file streaming and transfer of medical images or records.
med-supp2400312.2UnknownBuilt-inAs neededmed-supp operates on port 24003 and delivers supplemental data in medical information systems.
med-ovw2400412.2UnknownBuilt-inAs neededmed-ovw operates on port 24004 and manages overview and status updates in medical system dashboards.
med-ci2400512.2UnknownBuilt-inAs neededmed-ci operates on port 24005 and enables clinical interface services in integrated medical information systems.
med-net-svc2400612.2UnknownBuilt-inAs neededmed-net-svc operates on port 24006 and supports secure network services in medical environments.

Was this information helpful?