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
d-fence855512.2UnknownBuilt-inAs neededd-fence operates on port 8555 and is used by D-Fence for network security or firewall services.
enc-tunnel856712.2UnknownBuilt-inAs neededenc-tunnel operates on port 8567 and supports ENC Tunnel for encrypted tunneling of network traffic.
asterix860012.2UnknownBuilt-inAs neededasterix operates on port 8600 and is used for transmitting radar and surveillance data in the EUROCONTROL ASTERIX format.
canon-cpp-disc860912.2UnknownBuilt-inAs neededCanon Printer Protocol Discovery used to detect Canon network printers.
canon-mfnp861012.2UnknownBuilt-inAs neededCanon Multi-Function Peripheral protocol for faxing, scanning, and status updates.
canon-bjnp1861112.2UnknownBuilt-inAs neededCanon BJNP protocol for network printing over TCP/IP (port 8611).
canon-bjnp2861212.2UnknownBuilt-inAs neededCanon BJNP protocol (port 8612) used for print job transmission.
canon-bjnp3861312.2UnknownBuilt-inAs neededCanon BJNP protocol (port 8613) used in scanning or printer configuration.
canon-bjnp4861412.2UnknownBuilt-inAs neededCanon BJNP protocol (port 8614) for additional Canon device control.
imink861512.2UnknownBuilt-inAs neededimink operates on port 8615 and is used for communication in IMINK media or messaging services.
msi-cps-rm867512.2UnknownBuilt-inAs neededmsi-cps-rm operates on port 8675 and supports CPS resource management communication in MSI platforms.
msi-cps-rm-disc867512.2UnknownBuilt-inAs neededmsi-cps-rm-disc operates on port 8675 and enables resource management service discovery in MSI CPS environments.
sun-as-jmxrmi868612.2UnknownBuilt-inAs neededsun-as-jmxrmi operates on port 8686 and provides remote management for Sun Application Servers via JMX over RMI.
vnyx869912.2UnknownBuilt-inAs neededvnyx operates on port 8699 and is used for communication within the VNYX VoIP or messaging infrastructure.
nvc871112.2UnknownBuilt-inAs needednvc operates on port 8711 and enables streaming or conferencing control in NVC (Network Video Communication) systems.
dtp-net873212.2UnknownBuilt-inAs neededdtp-net operates on port 8732 and supports distributed test protocol communications in diagnostics networks.
ibus873312.2UnknownBuilt-inAs neededibus operates on port 8733 and enables inter-process messaging and component communication in desktop environments.
dey-keyneg875012.2UnknownBuilt-inAs neededdey-keyneg operates on port 8750 and facilitates key negotiation and secure session setup for DEY communication.
mc-appserver876312.2UnknownBuilt-inAs neededmc-appserver operates on port 8763 and provides application server communication in MC middleware environments.
openqueue876412.2UnknownBuilt-inAs neededopenqueue operates on port 8764 and manages queueing for distributed or asynchronous application messaging.

Was this information helpful?