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
lds-distrib654312.2UnknownBuilt-inAs neededlds-distrib operates on port 6543 and handles data distribution in LDS directory service frameworks.
lds-dump654412.2UnknownBuilt-inAs neededlds-dump operates on port 6544 and provides data extraction services in LDS (Local Directory Service) environments.
apc-6547654712.2UnknownBuilt-inAs neededAPC PowerChute Network Shutdown protocol used for UPS monitoring and remote shutdown over port 6547.
apc-6548654812.2UnknownBuilt-inAs neededAPC PowerChute port for UPS monitoring and remote power management.
apc-6549654912.2UnknownBuilt-inAs neededapc-6549 operates on port 6549 and supports device communication in APC (American Power Conversion) power management systems.
fg-sysupdate655012.2UnknownBuilt-inAs neededfg-sysupdate operates on port 6550 and supports FG System Update for firmware or software updates in FG devices.
sum655112.2UnknownBuilt-inAs neededsum operates on port 6551 and supports Software Update Management communication for patching and system updates.
xdsxdm655812.2UnknownBuilt-inAs neededxdsxdm operates on port 6558 and is used for device management communication in extended data service environments.
sane-port656612.2UnknownBuilt-inAs neededsane-port operates on port 6566 and supports SANE (Scanner Access Now Easy) protocol for accessing network scanners.
canit_store656812.2UnknownBuilt-inAs neededCanIt protocol for managing quarantined email and spam filtering storage.
rp-reputation656812.2UnknownBuilt-inAs neededrp-reputation operates on port 6568 and handles IP or domain reputation queries in security platforms.
affiliate657912.2UnknownBuilt-inAs neededaffiliate operates on port 6579 and handles tracking or coordination services in affiliate marketing networks.
parsec-master658012.2UnknownBuilt-inAs neededparsec-master operates on port 6580 and provides session and control coordination in Parsec server configurations.
parsec-peer658112.2UnknownBuilt-inAs neededparsec-peer operates on port 6581 and allows peer communication in Parsec gaming or distributed computing environments.
parsec-game658212.2UnknownBuilt-inAs neededparsec-game operates on port 6582 and is used for in-game communication or media streaming in Parsec.
joaJewelSuite658312.2UnknownBuilt-inAs neededjoajewelsuite operates on port 6583 and manages synchronization and messaging in Joa JewelSuite geological modeling software.
mshvlm660012.2UnknownBuilt-inAs neededmshvlm operates on port 6600 and supports Microsoft Hyper-V Live Migration services.
mstmg-sstp660112.2UnknownBuilt-inAs neededmstmg-sstp operates on port 6601 and supports Microsoft SSTP connections in secure tunnel environments.
wsscomfrmwk660212.2UnknownBuilt-inAs neededwsscomfrmwk operates on port 6602 and supports secure communication within IBM WebSphere Service Component Framework.
ktelnet662312.2UnknownBuilt-inAs neededktelnet operates on port 6623 and is a secure or extended version of the Telnet protocol used in private systems.

Was this information helpful?