rtiddsspy getting data traffic from (supposed) unknown multicasts (?)

1 post / 0 new
Offline
Last seen: 8 months 2 days ago
Joined: 01/07/2015
Posts: 5
rtiddsspy getting data traffic from (supposed) unknown multicasts (?)

I have many multicasts (Multicast Map QoS) in my domain. Qos multicast addresses seem to be correctly set in both Participant and DataReader QoS as 239.192...family addresses. The address 239.255.01 is still the default DDS discovery multicast in my network.

And they actually seem to be working fine, once I also see (after running my DDS apps) those multicast addresses listed in both two of my ethernet interfaces as "netsstat -g" Linux command. This is what netstat gets on each hosts of my network:

1) In host1:

IPv6/IPv4 Group Memberships
Interface       CntRef Group
--------------- ------ ---------------------

enp5s0          2      239.192.120.5
enp5s0          40     239.192.120.3
enp5s0          7      239.192.130.1
enp5s0          46     239.192.120.1
enp5s0          7      239.192.110.1
enp5s0          7      239.192.100.1
enp5s0          51     239.255.0.1

eno1            2      239.192.120.5
eno1            40     239.192.120.3
eno1            7      239.192.130.1
eno1            46     239.192.120.1
eno1            7      239.192.110.1
eno1            7      239.192.100.1
eno1            51     239.255.0.1

2) In host 2:

IPv6/IPv4 Group Memberships
Interface       CntRef Group
--------------- ------ ---------------------

enp5s0          2      239.192.120.5
enp5s0          46     239.192.120.2
enp5s0          7      239.192.130.1
enp5s0          52     239.192.120.1
enp5s0          7      239.192.110.1
enp5s0          7      239.192.100.1
enp5s0          57     239.255.0.1

eno1            2      239.192.120.5
eno1            46     239.192.120.2
eno1            7      239.192.130.1
eno1            52     239.192.120.1
eno1            7      239.192.110.1
eno1            7      239.192.100.1
eno1            57     239.255.0.1

As you can see above, "239.192.120.3" is present only in host1 and "239.192.120.2" only in host2. Considering that in my DDS Participant/DataReaders QoS topics begining with "A*" are correctly mapped to muticast "239.192.120.3" in host1 (above) and topic "B*" are also correctly mapped to "239.192.120.2", the question is:

>>> When I run rtiddsspy, in host1, I see not only discovery packages (Info field 'A sB' with A="R"/"W") - thats ok, but ALSO data packages (A="d"/"D") comming from a multicast which only exist in host2... In other words, rtiddsspy in host1 sees "B*" topics and rtiddsspy in host2 sees "A*" topics??!!?! Is it correct/previsible that rtiddsspy is able to get data ("d"/"D") packages maped to a multicast that it is not present in that host? Or there might be a mistake in my multicast map config/use?

Thanks!

Julio.