multicast

Note: Applies to RTI Connext 4.x and above RTI Connext 4.x and above uses a default multicast time-to-live (TTL) value of 1. This means that, by default, multicast traffic will not cross subnet boundaries. The TTL value can be adjusted in the transport property. Method One for modifying the TTL ( ...
14018 reads — 0 comments
Note: Applies to NDDS 3.x For machines with multiple NICs, it is sometimes useful to specify which NIC(s) to communicate over. Multicast packets will be sent through all interfaces that satisfy the following criteria: It is enabled for multicast NDDS is configured to use it Enabling a NIC for ...
4042 reads — 0 comments
Prior to RTI Data Distribution Service version 4.4, receiving data over multicast could only be configured on the reader side. The reader Qos specifies to the writer that it wants to receive data using a multicast address. Starting with RTI Data Distribution Service 4.4, in addition to the ...
9882 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above Yes, RTI Connext will cause IGMP messages to be sent, allowing routers to appropriately handle multicast traffic delivery. The RTI code does not send the IGMP messages itself, but the host's network stack should send them when needed. When RTI ...
5707 reads — 0 comments
Note: The ports used are different between RTI Connext 4.x and NDDS 3.x. RTI Connext The built-in UDP transport in RTI Connext 4.x and above uses port numbers that are based on the domain ID and participant ID. Because the RTPS spec changed, the mapping is different before and after Version 4.2 of ...
43101 reads — 4 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. Many operating systems, including Linux, limit the number of multicast group memberships that a machine can belong to simultaneously. (A "multicast group membership" indicates that a machine is listening to messages for a specific multicast IP ...
17044 reads — 0 comments

Pages

Subscribe to RSS - multicast