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
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.
nilinkanalyst2590212.2UnknownBuilt-inAs needednilinkanalyst operates on port 25902 and facilitates data analysis and flow control in NI Link Analyzer tools.
niprobe2590312.2UnknownBuilt-inAs neededniprobe operates on port 25903 and enables network probing or diagnostics in NI (National Instruments) environments.
bf-game2595412.2UnknownBuilt-inAs neededBattlefield Game protocol used by clients to communicate with multiplayer game servers.
bf-master2595512.2UnknownBuilt-inAs neededBattlefield Master Server protocol used to manage server lists and matchmaking.
quake2600012.2UnknownBuilt-inAs neededquake operates on port 26000 and supports Quake for multiplayer communication in the Quake game series.
scscp2613312.2UnknownBuilt-inAs neededscscp operates on port 26133 and enables communication using the Symbolic Computation Software Composability Protocol.
wnn6-ds2620812.2UnknownBuilt-inAs neededwnn6-ds operates on port 26208 and provides dictionary server functionality for the Wnn6 input system, enabling linguistic data access.

Was this information helpful?