Dynamic TCP Transport: Parameters Reference
The following tables describe the parameters specific to dynamic TCP transports and secure dynamic TCP transports in the configuration interface.
For web API access to transport definitions, see Transport Definition Objects.
| GUI Parameter | JSON Attribute | Description |
|---|---|---|
| Mode | mode | Required.
Select a mode from the drop-down menu: mesh, listen, or connect. For the meaning of these values, see Dynamic TCP Transport. |
| Group | virtual_name | Required when the mode is either listen or connect.
The group name ties together a listen end and a connect end, decoupling these definitions from the host and port. |
| Subnet Mask | subnet_mask | Optional.
Limit the hardware interfaces that this TCP transport can use. When network administrators allocate subnets for specific purposes, use this parameter to comply. Specify a IPv4 or IPv6 CIDR mask. For example, in IPv4: 192.168.2.0/24. In IPv6: 2001:db8::/32. |
| Port | port | Optional.
Designate a specific port to establish a TCP bus. When zero or absent, dynamic TCP transports use ephemeral listen ports to establish a bus. A firewall can thwart this mechanism. To circumvent the obstacle, designate a specific port for this purpose and arrange for the firewall to open that port. When present, all applications that use the transport definition bind this port to establish a bus. But only one application per host computer can bind this listen port. Notice this implicit restriction: if a dynamic TCP transport definition in either mesh or listen mode specifies a port, then only one application per host computer can use that transport definition. |