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
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.
cslg2475412.2UnknownBuilt-inAs neededcslg operates on port 24754 and supports communication in CSLG monitoring systems.
assoc-disc2485012.2UnknownBuilt-inAs neededDevice association discovery protocol, used in IoT or peripheral pairing systems.
find2492212.2UnknownBuilt-inAs neededfind operates on port 24922 and enables service discovery and location-based search in distributed networks.
icl-twobase12500012.2UnknownBuilt-inAs neededicl-twobase1 operates on port 25000 and supports communication in ICL TwoBase database or application server cluster.
icl-twobase22500112.2UnknownBuilt-inAs neededicl-twobase2 operates on port 25001 and enables failover or secondary services in ICL TwoBase systems.
icl-twobase32500212.2UnknownBuilt-inAs neededicl-twobase3 operates on port 25002 and supports communication in ICL TwoBase clustered environments for redundancy and load balancing.
icl-twobase42500312.2UnknownBuilt-inAs neededicl-twobase4 operates on port 25003 and supports additional node communication in ICL TwoBase server clusters.
icl-twobase52500412.2UnknownBuilt-inAs neededicl-twobase5 operates on port 25004 and allows for extended redundancy and load distribution in ICL clustered systems.
icl-twobase62500512.2UnknownBuilt-inAs neededicl-twobase6 operates on port 25005 and provides redundancy communication in ICL TwoBase clustered systems.
icl-twobase72500612.2UnknownBuilt-inAs neededicl-twobase7 operates on port 25006 and supports node-to-node messaging in ICL TwoBase cluster infrastructures.

Was this information helpful?