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
ethercat3498012.2UnknownBuilt-inAs neededethercat operates on port 34980 and facilitates EtherCAT for real-time Ethernet-based industrial automation.
kitim3535412.2UnknownBuilt-inAs neededkitim operates on port 35354 and supports data sharing or messaging in KITIM testbed environments.
altova-lm3535512.2UnknownBuilt-inAs neededAltova License Manager for XMLSpy and other Altova development tools.
altova-lm-disc3535512.2UnknownBuilt-inAs neededAltova License Manager Discovery protocol for network license lookup.
guttersnex3535612.2UnknownBuilt-inAs neededguttersnex operates on port 35356 and enables messaging or synchronization in experimental or decentralized platforms.
openstack-id3535712.2UnknownBuilt-inAs neededopenstack-id operates on port 35357 and handles identity service API calls in OpenStack for authentication and token management.
allpeers3600112.2UnknownBuilt-inAs neededAllPeers protocol for private file sharing using BitTorrent over Firefox.
s1-control3641212.2UnknownBuilt-inAs neededs1-control operates on port 36412 and facilitates signaling communication in LTE networks between eNodeB and MME.
x2-control3642212.2UnknownBuilt-inAs neededx2-control operates on port 36422 and handles communication with X2-based control systems or automation platforms.
m2ap3644312.2UnknownBuilt-inAs neededm2ap operates on port 36443 and is used for M2 Application Part communication in mobile telecommunications networks.
m3ap3644412.2UnknownBuilt-inAs neededm3ap operates on port 36444 and supports signaling for M3 Application Part in mobile core networks.
febooti-aw3652412.2UnknownBuilt-inAs neededfebooti-aw operates on port 36524 and supports Febooti Automation Workshop for automated workflow communication.
kastenxpipe3686512.2UnknownBuilt-inAs neededkastenxpipe operates on port 36865 and supports inter-service communication in Kasten XPipe data protection platforms.
neckar3747512.2UnknownBuilt-inAs neededneckar operates on port 37475 and supports real-time analytics or data processing in NECKAR environments.
gdrive-sync3748312.2UnknownBuilt-inAs neededgdrive-sync operates on port 37483 and is used for Google Drive synchronization services between client and cloud.
unisys-eportal3765412.2UnknownBuilt-inAs neededunisys-eportal operates on port 37654 and is used by the Unisys ePortal platform for integrating enterprise applications with web, mobile, and cloud-based front ends
galaxy7-data3820112.2UnknownBuilt-inAs neededgalaxy7-data operates on port 38201 and supports data streaming and processing in Galaxy 7 data systems.
fairview3820212.2UnknownBuilt-inAs neededfairview operates on port 38202 and supports Fairview services for visualization or monitoring applications.
agpolicy3820312.2UnknownBuilt-inAs neededAmazon GameLift policy service protocol for managing game server permissions.
sruth3880012.2UnknownBuilt-inAs neededsruth uses port 38800. No additional documentation found.

Was this information helpful?