I have a PC with a plethora of network adapters, and I'm trying to use one of the last ones listed to see DDS traffic. It's able to see the network participant, but not the topics. Admin console running on another PC without as many network adapters can see the topics
I've seen other posts here where it's been suggested that DDS will only allow you to use the first four network interfaces.
My thought is that this might have something to do with that (though if that is the case, why would it even see the domain participant?), so I tried creating an xml file that allowed only that last interface's ip address. This didn't work, but I'm not sure I did it correctly, as I experienced a warning on the Admin Console's console log window (although the message wasn't specific, it only said it read the XML file, but it still had WARNING severity, so I assume something was wrong with the XML file).
Here's what I see from the Admin Console on the PC that can't see everything:
The domain participant is seen, but not the topics:
If I run the Admin Console on the other PC without quite as many network adapters, I see my topics correctly:
I tried adding a QoS file on the PC running the failing analyzer. The goal was to allow only the network adapter, but it gave a warning message, and didn't seem to fix the problem:
The content of the xml file is:
<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://community.rti.com/schema/5.3.0/rti_dds_qos_profiles.xsd" version="5.3.0">
<qos_library name="CustomLibrary">
<participant_qos>
<property>
<value>
<element>
<name>dds.transport.UDPv4.builtin.parent.allow_interfaces</name>
<value>192.168.3.100</value>
</element>
</value>
</property>
</participant_qos>
</qos_library>
</dds>
1-
The Admin Console sees the Participant because by default Participant discovery is multicast. To limit what locators your PC announces you need to utilize the allow_interfaces filter. To achieve that refer to the following Knowledge Base article:
https://community.rti.com/kb/how-do-i-restrict-rti-connext-use-only-subset-interfaces
2- Prior to 5.3.1 the limit on locators was 4. It is now 16.
3- Error is Admin Console is an old bug. Workaround is to delete ../workspace/admin_console
4- XML Parse error due to malformed XML. Refer to RTI_ConnextDDS_CoreLibraries_UsersManual.pdf section 18.1 Example XML File. You forgot the qos__profile tag.
Thank you, irwin, it sounds like having too many network devices is not my problem, therefore I don't think I need to set the QoS, or mess with XML files. (?)
What, then, could be preventing my topics from being discovered? I believe firewall is not an issue on this network adapter.
The most likely reason for the case where the Participant is detected, but not the topics ( ie readers/writers is a firewall issue. To verify my hypothesis I suggest that you run rtiddsping as follows:
Publishing Machine PC that you ran Admin Console
rtiddsping -peer <PC IP address> rtiddsping -subscriber -peer <Publishing Machine IP address>
The behavior that Participant is detected in Admin console but not the topics, readers/writers - is this because of using Connext Micro?
The rtiddsping works between the publishing machine and the host that runs the admin console but yet the topics and reader/writers that use Connext Micro are not visible in the admin console.
If it is because of using Connext Micro, is there any mechanism to get these shown in admin console? Any inputs would be highly appreciated.
Generally, the default Micro settings needs to be adapted to work well with Admin Console. Check out these docs:
https://community.rti.com/static/documentation/connext-micro/2.4.14/doc/html/usersmanual/micro_core.html (Chapter 6, specifically Section 6.6)
https://community.rti.com/static/documentation/connext-micro/3.0.3/doc/html/usersmanual/micro_core.html (Section 6.7)
Regards,
Bob