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
indura315612.2Network servicesBuilt-inAs neededA protocol for Indura, supporting Indura networked communication systems.
e3consultants315712.2Network servicesBuilt-inAs neededA protocol for E3 Consultants, a proprietary consulting network service.
stvp315812.2Network servicesBuilt-inAs neededSecure Tunnel VPN protocol provides lightweight encrypted connections.
navegaweb-port315912.2Network servicesBuilt-inAs neededEnables access to NavegaWeb management GUI for ISP or content routers.
tip-app-server316012.2Network servicesBuilt-inAs neededTIP App Server protocol facilitates transaction coordination in distributed environments.
doc1lm316112.2Network servicesBuilt-inAs neededA license management protocol, tied to document management software like DOC1, ensuring authorized usage.
sflm316212.2Network servicesBuilt-inAs neededSoftware Factory License Manager protocol for syncing entitlements.
res-sap316312.2Network servicesBuilt-inAs neededResource SAP protocol syncs asset data across SAP enterprise resource planning modules.
imprs316412.2Network servicesBuilt-inAs neededA protocol for IMPRS (Integrated Management Protocol Reporting Service), reporting data.
newgenpay316512.2Network servicesBuilt-inAs neededNewGenPay protocol handles secure retail and mobile point-of-sale transactions.
sossecollector316612.2Network servicesBuilt-inAs neededSOSSE Collector protocol aggregates logs and telemetry from secure endpoints.
nowcontact316712.2Network servicesBuilt-inAs neededNowContact syncs personal contact databases across client applications.
poweronnud316812.2Network servicesBuilt-inAs neededPowerOn Network Update Daemon protocol manages firmware and config sync.
serverview-as316912.2Network servicesBuilt-inAs neededFujitsu ServerView Agent Service protocol manages hardware health and telemetry.
serverview-asn317012.2Network servicesBuilt-inAs neededASN extension of ServerView enables SNMP-style notifications for enterprise monitoring.
serverview-gf317112.2Network servicesBuilt-inAs neededFujitsu ServerView Global Framework sync protocol for asset and health reporting.
serverview-rm317212.2Network servicesBuilt-inAs neededFujitsu ServerView Remote Management protocol for out-of-band telemetry and control.
serverview-icc317312.2Network servicesBuilt-inAs neededFujitsu ServerView Integrated Console Control protocol for BIOS and remote media sync.
armi-server317412.2Network servicesBuilt-inAs neededA protocol for ARMI (Application Remote Management Interface) server, managing apps remotely.
t1-e1-over-ip317512.2Network servicesBuilt-inAs neededEncapsulates T1/E1 telecom lines over IP networks for legacy interconnection.

Was this information helpful?