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
tcc-http2468012.2Web browsingBuilt-inAs needed a tool or script performing HTTP requests, potentially related to telecommunications carrier control.
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.
icl-twobase82500712.2UnknownBuilt-inAs neededicl-twobase8 operates on port 25007 and enables additional service communication for ICL TwoBase environments.
icl-twobase92500812.2UnknownBuilt-inAs neededicl-twobase9 operates on port 25008 and supports failover or load balancing in large ICL TwoBase configurations.
icl-twobase102500912.2UnknownBuilt-inAs neededicl-twobase10 operates on port 25009 and provides alternate node access for ICL TwoBase cluster configuration.
rna2547112.2UnknownBuilt-inAs neededrna operates on port 25471 and enables communication in RNA (Remote Network Access) platforms for secure remote access and system management.
sauterdongle2557612.2UnknownBuilt-inAs neededsauterdongle operates on port 25576 and enables secure communication for Sauter automation hardware using a hardware dongle.
idtp2560412.2UnknownBuilt-inAs neededidtp operates on port 25604 and is used for secure or structured data transfer in IDTP-based custom environments.
vocaltec-hos2579312.2UnknownBuilt-inAs neededvocaltec-hos operates on port 25793 and supports host services for VocalTec communication platforms.
tasp-net2590012.2UnknownBuilt-inAs neededtasp-net operates on port 25900 and supports communication in TASP network systems for telemetry or secure application services.
niobserver2590112.2UnknownBuilt-inAs neededniobserver operates on port 25901 and provides real-time data observation in National Instruments distributed systems.
←1…291292293294295…319→