Initial peers configuration whith Participant ID unknown (#295)

* Refs #12776: clarify initial peers configuration when the Participant ID is unknown Signed-off-by: JLBuenoLopez-eProsima <[email protected]> * Refs #12776: correct behavior of initial peers without setting port Signed-off-by: JLBuenoLopez-eProsima <[email protected]> * Refs #12776: fix CI Signed-off-by: JLBuenoLopez-eProsima <[email protected]>
eProsima · Oct 28, 2021 · 46046e9 · 46046e9
1 parent 45086b8
commit 46046e9
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 0 deletions.
diff --git a/docs/fastdds/discovery/simple.rst b/docs/fastdds/discovery/simple.rst
@@ -141,6 +141,13 @@ By default *eProsima Fast DDS* uses as initial peers the Metatraffic Multicast L
 The following constitutes an example configuring an Initial Peers list with one peer on host 192.168.10.13 with
 DomainParticipant ID 1 in domain 0.
 
+.. note::
+   There is also the possibility of not defining the initial peer port.
+   In this case, the discovery information would be sent to every port ranging from `participantID` zero to the
+   ``maxInitialPeersRange`` value set in the :ref:`transport_transportApi_transportDescriptor`.
+   Consequently, setting this value to at least the maximum expected number of DomainParticipants will ensure discovery
+   and communication.
+
 +----------------------------------------------------------------------------------------------------------------------+
 | **C++**                                                                                                              |
 +----------------------------------------------------------------------------------------------------------------------+

diff --git a/docs/fastdds/use_cases/wifi/initial_peers.rst b/docs/fastdds/use_cases/wifi/initial_peers.rst
@@ -16,6 +16,10 @@ on host ``192.168.10.13`` with participant ID ``1`` in domain ``0``.
     the `RTPS v2.2 standard`_.
     Refer to :ref:`listening_locators_defaultPorts` to learn about these standard port numbers.
 
+    If the participant ID is not known, setting :ref:`transport_transportApi_transportDescriptor`
+    ``maxInitialPeersRange`` to at least the maximum expected number of DomainParticipants will ensure discovery and
+    communication.
+
 
 +---------------------------------------------------------+
 | **C++**                                                 |