multicast

Endpoint Discovery uses either unicast or multicast, depending on the situation. First, some background: Endpoint Discovery is the process used by endpoints (that is, DataReaders and DataWriters ) to locate each other before they can begin to communicate user data. When a DomainParticipant is ...
2653 reads — 0 comments
Multicast over UDPv4 can be used for data transfer between applications that are running on the same machine, even if shared memory is enabled. RTI's Connext DDS provides various transports, which can be configured using the USER_QOS_PROFILES.xml file. The most commonly used transports are shared ...
2327 reads — 0 comments
RTI Connext DDS uses multicast for the discovery process in the default setting. When a host needs to join a multicast group, the network stack of the host sends out an IGMP Membership Report message also known as the join message. These messages are forwarded through the LAN to the local IGMP ...
4955 reads — 0 comments
In short, by default, one copy of a sample is sent per transport locator, where a transport locator uniquely identifies a transport-level destination and is composed of <transport class>://<transport address>: <communication port> . For example, for UDPv4 a transport locator could ...
5499 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.3x and above, Both rtiddsping and rtiddsspy can be configured to use multicast for discovery announcements by specifying a multicast address as part of the initial peer list (using -preer <PEER> ). However, rtiddsping and rtiddsspy do not have ...
4081 reads — 0 comments
This message can be recieved when creating a new reader listening on a multicast group: setsockopt(ADD_MEMBERSHIP) error 0X62 The hex code may differ across platforms — EADDRINUSE is 98 on Linux, 125 on Solaris — check your system's errno.h to be sure. RTI middleware can share receive-resources ...
3591 reads — 1 comment
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. The LynxOS 4.0 IP stack (and many other BSD-derived network stacks) will fail to send multicast messages unless there is an entry in the routing table that matches the destination multicast IP address. In practice, this means that either: a ...
2917 reads — 0 comments
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 ( ...
9084 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 ...
2741 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 ...
7142 reads — 0 comments

Pages

Subscribe to RSS - multicast