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
sun-sr-jms648412.2UnknownBuilt-inAs neededsun-sr-jms operates on port 6484 and supports Java Messaging Service integration within Sun Service Registry.
sun-sr-iiop648512.2UnknownBuilt-inAs neededsun-sr-iiop operates on port 6485 and supports standard CORBA IIOP protocol messaging in Sun Service Registry.
sun-sr-iiops648612.2UnknownBuilt-inAs neededsun-sr-iiops operates on port 6486 and enables CORBA IIOP Secure communication in Sun Service Registry infrastructure.
sun-sr-iiop-aut648712.2UnknownBuilt-inAs neededsun-sr-iiop-aut operates on port 6487 and provides automatic CORBA IIOP configuration in Sun-based service platforms.
sun-sr-jmx648812.2UnknownBuilt-inAs neededsun-sr-jmx operates on port 6488 and allows Java Management Extensions (JMX) monitoring in Sun Service Registry systems.
sun-sr-admin648912.2UnknownBuilt-inAs neededsun-sr-admin operates on port 6489 and provides administrative access and configuration for Sun Service Registry environments.
boks650012.2UnknownBuilt-inAs neededBOKS security protocol for access control and centralized authentication in Unix environments.
boks_servc650112.2UnknownBuilt-inAs neededBOKS service control process managing system-level access permissions.
boks_servm650212.2UnknownBuilt-inAs neededBOKS main server daemon managing identities and policy enforcement.
boks_clntd650312.2UnknownBuilt-inAs neededBOKS client daemon used to enforce user authentication on endpoints.
badm_priv650512.2UnknownBuilt-inAs neededbadm_priv operates on port 6505 and handles secure or internal communication within Broadcast Administration networks.
badm_pub650612.2UnknownBuilt-inAs neededbadm_pub operates on port 6506 and manages public-facing services for Broadcast Administration systems.
bdir_priv650712.2UnknownBuilt-inAs neededbdir_priv operates on port 6507 and handles private directory synchronization or data exchange in enterprise environments.
bdir_pub650812.2UnknownBuilt-inAs neededbdir_pub operates on port 6508 and manages directory publishing or file sharing in specialized data networks.
mgcs-mfp-port650912.2UnknownBuilt-inAs neededmgcs-mfp-port operates on port 6509 and supports multi-function printer communication in MGCS (Managed Gateway Control System).
mcer-port651012.2UnknownBuilt-inAs neededmcer-port operates on port 6510 and provides control and logging in MCER (Managed Communication and Event Reporting) systems.
dccp-udp651112.2UnknownBuilt-inAs neededdccp-udp operates on port 6511 and is used by DCCP over UDP for encapsulating DCCP in UDP packets.
netconf-tls651312.2UnknownBuilt-inAs needednetconf-tls operates on port 6513 and provides secure configuration management over TLS in NETCONF-compliant devices.
syslog-tls651412.2UnknownBuilt-inAs neededsyslog-tls operates on port 6514 and enables the transmission of syslog messages over TLS for secure logging and monitoring.
elipse-rec651512.2UnknownBuilt-inAs neededelipse-rec operates on port 6515 and supports Elipse REC for remote execution control in Elipse systems.

Was this information helpful?