RTI Secure Wan Transport  Version 6.0.0
 All Data Structures Functions Variables Typedefs Enumerations Groups Pages
Configure WAN Transport with Property QoS Policy

Predefined strings that can be used to configure the WAN Transport plugin through the Property QoS Policy of the DomainParticipant. More...

Predefined strings that can be used to configure the WAN Transport plugin through the Property QoS Policy of the DomainParticipant.

Properties for Registering the WAN Transport
Property Name Description Required?
dds.transport.load_plugins Comma-separated strings indicating the prefix names of all plugins that will be loaded by RTI Connext. Up to 8 plugins may be specified. For example, "dds.transport.WAN.wan1".
In the following examples, <WAN_prefix> indicates the string that is used as a prefix in the property names for all the settings that are related to this WAN transport plugin. <WAN_prefix> must begin with "dds.transport." (such as "dds.transport.WAN.wan1").
YES
<WAN_prefix>.library Must set to "libnddstransportwan.so" (for UNIX/Solaris) or "nddstransportwan.dll" (for Windows). This library (and the dependent openssl libraries if security is turned on) needs to be in the path during run time for use by RTI Connext (in the LD_LIBRARY_PATH environment variable on UNIX/Solaris, in PATH for Windows) YES
<WAN_prefix>.create_function Must be set to "NDDS_Transport_WAN_create" . YES
<WAN_prefix>.aliases Used to register the transport plugin returned by NDDS_Transport_WAN_create() (as specified by <WAN_prefix>.create_function) to the domain participant. Refer to aliases_in parameter in NDDS_Transport_Support_register_transport() for details. Aliases should be specified as comma separated string, with each comma delimiting an alias. If it is not specified, <WAN_prefix> is used as the default alias for the plugin

NO

<WAN_prefix>.verbosity Set to a number specifying the verbosity of log messages from the transport. Possible values include:
  • -1: silent
  • 0 (default): errors only
  • 1: errors and warnings
  • 2: local status
  • 5 or higher: all messages

NO

<WAN_prefix>.parent.parent.address_bit_count See NDDS_Transport_Property_t::address_bit_count
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.parent.properties_bitmap See NDDS_Transport_Property_t::properties_bitmap
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.parent.gather_send_buffer_count_max See NDDS_Transport_Property_t::gather_send_buffer_count_max
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.parent.message_size_max See NDDS_Transport_Property_t::message_size_max
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.parent.allow_interfaces See NDDS_Transport_Property_t::allow_interfaces_list and NDDS_Transport_Property_t::allow_interfaces_list_length.
Interfaces should be specified as comma separated string, with each comma delimiting an interface. For example, "127.0.0.1,eth0"
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.parent.deny_interfaces See NDDS_Transport_Property_t::deny_interfaces_list and NDDS_Transport_Property_t::deny_interfaces_list_length.
Interfaces should be specified as comma separated string, with each comma delimiting an interface. For example, "127.0.0.1,eth0"
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.

NO

<WAN_prefix>.parent.send_socket_buffer_size See NDDS_Transport_UDPv4_Property_t::send_socket_buffer_size
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.recv_socket_buffer_size See NDDS_Transport_UDPv4_Property_t::recv_socket_buffer_size Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value. NO
<WAN_prefix>.parent.unicast_enabled See NDDS_Transport_UDPv4_Property_t::unicast_enabled
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.

NO

<WAN_prefix>.parent.ignore_loopback_interface See NDDS_Transport_UDPv4_Property_t::ignore_loopback_interface Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value. NO
<WAN_prefix>.parent.ignore_nonrunning_interfaces [DEPRECATED] See NDDS_Transport_UDPv4_Property_t::ignore_nonrunning_interfaces
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.no_zero_copy [DEPRECATED] See NDDS_Transport_UDPv4_Property_t::no_zero_copy
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.send_blocking See NDDS_Transport_UDPv4_Property_t::send_blocking
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.transport_priority_mask See NDDS_Transport_UDPv4_Property_t::transport_priority_mask
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.transport_priority_mapping_low See NDDS_Transport_UDPv4_Property_t::transport_priority_mapping_low
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.parent.transport_priority_mapping_high See NDDS_Transport_UDPv4_Property_t::transport_priority_mapping_high
Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_PROPERTY_DEFAULT for default value.
NO
<WAN_prefix>.enable_security See NDDS_Transport_WAN_Property_t::enable_security YES if you want to use security. NO otherwise.
<WAN_prefix>.recv_decode_buffer_size See NDDS_Transport_WAN_Property_t::recv_decode_buffer_size NO
<WAN_prefix>.port_offset See NDDS_Transport_WAN_Property_t::port_offset NO
<WAN_prefix>.dtls_handshake_resend_interval See NDDS_Transport_WAN_Property_t::dtls_handshake_resend_interval

NO

<WAN_prefix>.tls.verify.ca_file See NDDS_Transport_TLS_Verification::ca_file If you want to use security, either ca_file or ca_path is required. NO otherwise.
<WAN_prefix>.tls.verify.ca_path See NDDS_Transport_TLS_Verification::ca_path If you want to use security, either ca_file or ca_path is required. NO otherwise.
<WAN_prefix>.tls.verify.verify_depth See NDDS_Transport_TLS_Verification::verify_depth NO
<WAN_prefix>.tls.verify.verify_peer See NDDS_Transport_TLS_Verification::verify_peer NO
<WAN_prefix>.tls.verify.verify_callback See NDDS_Transport_TLS_Verification::callback
This can be set to one of three values:
NO
<WAN_prefix>.tls.cipher.cipher_list See NDDS_Transport_TLS_Ciphers::cipher_list NO
<WAN_prefix>.tls.cipher.dh_param_files See NDDS_Transport_TLS_Ciphers::dh_param_files.
For example: "foo.h:512,bar.h:256" means
dh_param_files[0].file = foo.h,
dh_param_files[0].bits = 512,
dh_param_files[1].file = bar.h,
dh_param_files[1].bits = 256,
NO
<WAN_prefix>.tls.cipher.engine_id See NDDS_Transport_TLS_Ciphers::engine_id NO
<WAN_prefix>.tls.identity.certificate_chain_file See NDDS_Transport_TLS_Identity::certificate_chain_file YES if you want to use security. NO otherwise.
<WAN_prefix>.tls.identity.private_key_password See NDDS_Transport_TLS_Identity::private_key_password NO
<WAN_prefix>.tls.identity.private_key_file See NDDS_Transport_TLS_Identity::private_key_file NO
<WAN_prefix>.tls.identity.rsa_private_key_file See NDDS_Transport_TLS_Identity::rsa_private_key_file NO
<WAN_prefix>.transport_instance_id A set of up to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_WAN_TRANSPORT_INSTANCE_ID_LENGTH comma-separated values to specify the elements of the array. If less than the full array is specified, it will be right-aligned.
For example, the string "01,02" results in the array being set to {0,0,0,0,0,0,0,0,0,0,1,2}
See NDDS_Transport_WAN_Property_t::transport_instance_id
YES
<WAN_prefix>.interface_address See NDDS_Transport_WAN_Property_t::interface_address NO
<WAN_prefix>.server See NDDS_Transport_WAN_Property_t::server YES
<WAN_prefix>.server_port See NDDS_Transport_WAN_Property_t::server_port NO
<WAN_prefix>.stun_retransmission_interval See NDDS_Transport_WAN_Property_t::stun_retransmission_interval NO
<WAN_prefix>.stun_number_of_retransmissions See NDDS_Transport_WAN_Property_t::stun_number_of_retransmissions NO
<WAN_prefix>.stun_liveliness_period See NDDS_Transport_WAN_Property_t::stun_liveliness_period

NO


RTI Secure Wan Transport Version 6.0.0 Copyright © Sun Mar 3 2019 Real-Time Innovations, Inc