Readers & writers are unable to communicate using multicast

2 posts / 0 new
Last post
Joined: 12/19/2013
Posts: 5
Readers & writers are unable to communicate using multicast


My DDS project (v 5.0)  has been working fine using shared memory in a standalong linux machine.  Now, we want to change to use multicast to communicate over the network on multiple machines.  I have changed my QOS profile as followed for multicast communication.  After the change, I can see that shared memory segments are not created when starting up the DDS processes so I know that it is not using shared memory anymore.  If I do netstat -g, I can see the multicast group is showing with the number of reference count increases.  However, I am not able to get the reader and writer to communicate with each other via multicast. Do I need to change anything in the code support multicast communincation? 

<participant_qos name="Base_participant_QOS">     









      <datareader_qos name="Base_datareader_QOS">
             <element>           <!-- Must be a valid multicast address-->   



> [system@localhost scripts]$ netstat -g
IPv6/IPv4 Group Memberships
Interface       RefCnt Group
--------------- ------ ---------------------
lo              1
eth0            4
eth0            1
eth0            1
virbr0          4
virbr0          1
virbr0          1
lo              1      ff02::1
eth0            1      ff02::1:ff15:1a5f
eth0            1      ff02::1
virbr0          1      ff02::1
virbr0-nic      1      ff02::1




Joined: 01/31/2011
Posts: 37

Hi Michelle,

It looks like you've made the minimum changes necessary to support multicast.  Have you verified that the DataReader and DataWriter have discovered each other? You can check this via the listener callbacks or status structures.

If they have not discovered each other, you'll want to verify that your network can support multicast communication.  You can use rtiddsping to verify that both machines can discover each other over DDS.  If rtiddsping does not work, then the network is preventing the connection.  Try just regular 'ping', and verify that you can reach the other machine.

If the network is indeed the cause, see this knowledge base article about common reasons: Why are my reader and writer applications unable to communicate?.

If the network shows no issues, then please let us know about the results of rtiddsping and the discovery match statuses.



Sumeet Shendrikar

Professional Services Team @ RTI