Publishers and Subscriber Discovery problem

3 posts / 0 new
Last post
Offline
Last seen: 3 weeks 4 days ago
Joined: 07/26/2019
Posts: 4
Publishers and Subscriber Discovery problem

I am stumped trying to get the Publisher and Subscriber to discover each other if my "Network Emulation" network is chosen.

I have two Virtual Machines VM04 (Subscriber) and VM05 (Publisher) and both OpenDDS and RTI installed on both.

One network path (the 172.16.*)   VM04 is 172.16.20.124 and VM05 is 172.16.59.31) has two DSRC deivces performing a wireless communication

Second Network Path is a network emulation layer, where the bandwidth and latency can be configured. In other words, there is software to control the network performance in this layer. 

Here is what works

1. OpenDDS (with DCPSInfoRepo on VM04) works in both environments (adusting /etc/hosts for controlling which IP address (thus network) is used for the two machines the network for discovery and data transmission

2. RTI DDS works on the DRSC path. I rename DSRC-USER_QOS_PROFILES.xml to USER_QOS_PROFIELS.xml and discovery and data exchange occurs

Here is what fails, and I cannot figure out why

RTI DDS, using Network-try2-USER_QOS_PROFILES (renamed) - the discovery never occurs.

I have used these tips and links..

a https://community.rti.com/kb/how-do-i-restrict-rti-connext-use-only-subset-interfaces

eliminate network connections (such as 10.0.0.* which is how I connect to the virtual machines)

https://community.rti.com/kb/i-put-my-machines-my-initial-peers-lists-why-don%E2%80%99t-they-discover-each-other - specifically case 2

and

c https://community.rti.com/kb/how-do-i-configure-rti-data-distribution-service-not-use-multicast

to disable multicast

and tried to understand d https://community.rti.com/forum-topic/multicast-and-discovery - but not sure how it applies

Any recommendations or changes to my Network-try-2 QOS profile for discovery to occur over this network path will be greatly appreciated.

Thanks

 

irwin's picture
Offline
Last seen: 3 weeks 3 days ago
Joined: 08/14/2010
Posts: 15

I would first think that you have an issue with the 192.168 network. I would suggest that you try with our utility rtiddsping.

Offline
Last seen: 3 weeks 4 days ago
Joined: 07/26/2019
Posts: 4

Irwin,

Thanks - alreeady resolved before exploring rtiddsping.

Network Admin adjusted some firewall rules for UDP