multicast

When using the multicast_mapping QoS, you may encounter this error: NDDS_Transport_UDP_share_recvresource_rrEA:setsockopt(ADD_MEMBERSHIP) error 0X69 This error usually indicates that you've exhaused the kernel parameter called igmp_max_memberships on Linux-like operating systems. The default for ...
281 reads — 0 comments
By default, RTI Connext Micro will let the Network stack select the interface that will be used to receive multicast traffic. This is done by simply using INADDR_ANY (which translates to 0.0.0.0) when setting the socket option to join a multicast group (that is IP_ADD_MEMBERSHIP). While this works ...
591 reads — 0 comments
There are three steps to take to configure Connext Micro not to use multicast. Set disable_auto_interface_config to true. Micro will scan the system for available interfaces and use them. Note, however, when this is set to true, Micro relies on just the manually added interfaces. Add an interface ...
1251 reads — 0 comments
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 ...
7228 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 ...
4677 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 ...
8333 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 ...
7929 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 ...
6186 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 ...
6105 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 ...
4546 reads — 0 comments

Pages

Subscribe to RSS - multicast