Refs #20629: Use whitelist to avoid interfaces translation problem

Signed-off-by: cferreiragonz <carlosferreira@eprosima.com>

Author: cferreiragonz

test/configuration/test_cases/test_95_tcpv4_cli.xml

@@ -1,6 +1,13 @@
 <?xml version="1.0" encoding="utf-8"?>
 <DS xmlns="http://www.eprosima.com/XMLSchemas/discovery-server" user_shutdown="false">
 
+    <!-- In order to avoid extra channel connections between TCP participants
+         we will use the whitelist to force the clients to send their locators
+         with localhost. Otherwise, the server would not reuse the initial
+         channel created and it might cause a failure in the connection,
+         depending of the value of the random logical port assigned.
+         This could be avoided by using default GUIDs. -->
+
     <clients>
         <client name="client1" profile_name="TCPv4_client_1" listening_port="0">
             <subscriber topic="topic1"/>
@@ -21,15 +28,21 @@
                 <transport_id>transport_client_1</transport_id>
                 <type>TCPv4</type>
                 <listening_ports>
-                    <port>42101</port>
+                    <port>0</port>
                 </listening_ports>
+                <interfaceWhiteList>
+                    <address>lo</address>
+                </interfaceWhiteList>
             </transport_descriptor>
             <transport_descriptor>
                 <transport_id>transport_client_2</transport_id>
                 <type>TCPv4</type>
                 <listening_ports>
-                    <port>42102</port>
+                    <port>0</port>
                 </listening_ports>
+                <interfaceWhiteList>
+                    <address>lo</address>
+                </interfaceWhiteList>
             </transport_descriptor>
         </transport_descriptors>
 

test/configuration/test_cases/test_96_tcpv6_cli.xml

@@ -21,15 +21,21 @@
                 <transport_id>transport_client_1</transport_id>
                 <type>TCPv6</type>
                 <listening_ports>
-                    <port>42101</port>
+                    <port>0</port>
                 </listening_ports>
+                <interfaceWhiteList>
+                    <address>::1</address>
+                </interfaceWhiteList>
             </transport_descriptor>
             <transport_descriptor>
                 <transport_id>transport_client_2</transport_id>
                 <type>TCPv6</type>
                 <listening_ports>
-                    <port>42102</port>
+                    <port>0</port>
                 </listening_ports>
+                <interfaceWhiteList>
+                    <address>::1</address>
+                </interfaceWhiteList>
             </transport_descriptor>
         </transport_descriptors>
 

test/configuration/test_cases/test_98_tcpv6_env_var.xml

@@ -5,7 +5,8 @@
          we will use the whitelist to force the clients to send their locators
          with localhost. Otherwise, the server would not reuse the initial
          channel created and it might cause a failure in the connection,
-         depending of the value of the random logical port assigned.  -->
+         depending of the value of the random logical port assigned.
+         This could be avoided by using default GUIDs. -->
 
     <servers>
         <server name="server" profile_name="TCPv6_server"/>