Hi,
I have 2 NICs installed on an Ubuntu server. One NIC connects to a private subnet router that only the Ubuntu server can access. The other NIC connects to an enterprise network. I would like participants on the Ubuntu server to only discover "local" participants (i.e. running on the same server) and participants created on the subnet. Likewise I want pariticpants on the subnet to only discover local participants and participants on the Ubuntu server. I am also using Routing Service on the Ubuntu server to publish some topics to a different domain on the enterprise network.
I tried using the pariticpant qos property dds.transport.UDPv4.builtin.parent.allow_interfaces to only have the subnet address (10.1.0.*) but then Routing Service doesn't discover pariticipants in the enterprise. I would like to use the peers list but I haven't found a way to indicate "all hosts" on the subnet. The number of hosts on the subnet is dynamic so I can't specify all the hosts. I've tried the following but the subnet participants aren't discovered (10.1.0.11 is the router address).
<discovery>
<initial_peers>
<element>builtin.udpv4://127.0.0.1,builtin.udpv4://10.1.0.11,builtin.shmem://</element>
</initial_peers>
<multicast_receive_addresses/>
</discovery>
Does anyone have an idea on how to do this?
Thanks,
Anne Fiore
Hi Anne,
What would be the reason why you made the "multicast_recieve_addresses" configuration empty?
Would you try it again after removing this setting? It may cause that your subnet participants would not be found dynamically.
If possible, would you provide how you set QoS in the Routing Serivce participants?
You said Routing Service doesn't discover participant in the enterprise after setting the subnet address (10.1.0.*).
Would you try to configure this setting only for the participant communicating with your subnet participants?
The setting may restrict the communications with participants in the enterprise.
I believe the Routing Service allows to set different QoS parameters for different participants (e.g. participant 1 for subnet and participant 2 for enterprise in your case)
Thanks,
Kyoungho
Hi Kyoungho,
Thanks for your ideas. I thought that if I removed multicast from initial_peers then I also had to clear multicast_receive_addresses....my mistake I was reading how to completely disable multicast. Now I can see how the server can keep the default multicast_receive_addresses so that participants on the subnet can still discover server participants. I don't need to include the subnet interface ip in the initial peers. As for the routing service, it was running with the same qos as the server so I think that's why it wasn't discovering participants on the enterprise network (no multicast receive). So now my server participants are being discovered by the subnet and enterprise since I am using the default multicast receive address.
Thanks again for your help.
Anne