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
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.
filesphere2424212.2UnknownBuilt-inAs neededfilesphere operates on port 24242 and supports Filesphere for distributed file sharing or storage.
vista-4gl2424912.2UnknownBuilt-inAs neededvista-4gl uses port 24249. No additional documentation found.
ild2432112.2UnknownBuilt-inAs neededild operates on port 24321 and enables remote device management in ILD-controlled environments.
hid2432212.2UnknownBuilt-inAs neededhid operates on port 24322 and facilitates device-level communication with Human Interface Devices over IP.
intel_rci2438612.2UnknownBuilt-inAs neededintel_rci operates on port 24386 and supports command and telemetry for Intel RCI control platforms.
tonidods2446512.2UnknownBuilt-inAs neededtonidods operates on port 24465 and is used by Tonido for device server communication, enabling remote access and file sharing.
binkp2455412.2UnknownBuilt-inAs neededBinkP protocol used in FidoNet message transfer over TCP/IP networks.
canditv2467612.2UnknownBuilt-inAs neededcanditv operates on port 24676 and is used for interactive television data communication in CandiTV systems.
flashfiler2467712.2UnknownBuilt-inAs neededflashfiler operates on port 24677 and supports database communication in Borland FlashFiler DBMS.
proactivate2467812.2UnknownBuilt-inAs neededproactivate operates on port 24678 and facilitates ProActivate for software or device activation services.

Was this information helpful?