interface white list #4046
Replies: 2 comments 3 replies
-
Hi @piniSolomon, thank you for using Fast DDS. You have to configure the transport descriptor in each of the pc's DDS applications. Let's call them pc A and pc B. Include the pc A's IP addresses (I guess that localhost would not be needed) in the pc A's participant transport descriptors (as explained in this section of the documentation), as you are configuring which of the available interfaces you want the participant A to communicate through. In pc B, you should create another XML file including the pc B's IP addresses in the B participant transport descriptors. Also looking at your configuration, the listening ports configuration will be ignored because it is only taken into account in TCP transports. |
Beta Was this translation helpful? Give feedback.
-
Hi @piniSolomon, There are several not necessary things in your transport descriptor. To achieve what you want you'd only need In addition, for the communication to work, both participants should be connected to at least one common LAN through which multicast works correctly (if it does not then you'd need to configure some other things), have you verified this? Sometimes the network configuration for virtual networks used between host and VM needs to explicitly enable multicast, and sometimes the out-of-the-box may have some firewall rules. |
Beta Was this translation helpful? Give feedback.
-
hi guys,
I'm getting familiar with the fast dds project I want to make use of the interfaceWhiteList element in the transport descriptor. Once I set values in the xml element the reader and writer do no match. The values im entering are the ip addresses of both pc the network.
I also tried to put only one IP for each pc and that didn't work also.
will be glad for some help with that
both pc's running ubuntu 20.04
the second pc is a VM using virtualbox
Beta Was this translation helpful? Give feedback.
All reactions