Issue with GNUnet Peer Communication Across Subnets

--00000000000056ea3406336e8c7c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Good morning,
I am reaching out regarding an issue with GNUnet that I haven=E2=80=99t bee=
n able
to resolve.
I am testing GNUnet in an emulated environment (GNS3), and I can get peers
to communicate locally (within the same subnet), but not =E2=80=9Cglobally=
=E2=80=9D across
routers and different subnets.
The routers are Debian machines with two network interfaces, IP forwarding
enabled, no firewall rules, one SNAT masquerade rule, and two DNAT rules
for port 2086 (both TCP and UDP).
Hosts in different networks can communicate correctly, and I can see the
address translation happening. The port also appears to be open, as
communication using netcat works as expected.
In the host configuration file, I have set EXTERNAL_ADDRESS=3D<public-ip>,
but this address is not being included in the peer=E2=80=99s HELLO message.
I also considered that the problem might be related to bootstrapping, so I
tried importing the HELLO of a peer not behind NAT (with only the =E2=80=9C=
public
IP=E2=80=9D) into the one behind NAT, but communication still does not work=
.
I would greatly appreciate any advice or suggestions on how to proceed.
Thank you for your time and support.

Kind regards,
Daniele

--00000000000056ea3406336e8c7c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>Good morning,<br>I am reaching out regarding an issue with GNUnet that=
 I haven=E2=80=99t been able to resolve.<br>I am testing GNUnet in an emula=
ted environment (GNS3), and I can get peers to communicate locally (within =
the same subnet), but not =E2=80=9Cglobally=E2=80=9D across routers and dif=
ferent subnets.<br>The routers are Debian machines with two network interfa=
ces, IP forwarding enabled, no firewall rules, one SNAT masquerade rule, an=
d two DNAT rules for port 2086 (both TCP and UDP).<br>Hosts in different ne=
tworks can communicate correctly, and I can see the address translation hap=
pening. The port also appears to be open, as communication using netcat wor=
ks as expected.<br>In the host configuration file, I have set EXTERNAL_ADDR=
ESS=3D&lt;public-ip&gt;, but this address is not being included in the peer=
=E2=80=99s HELLO message.<br>I also considered that the problem might be re=
lated to bootstrapping, so I tried importing the HELLO of a peer not behind=
 NAT (with only the =E2=80=9Cpublic IP=E2=80=9D) into the one behind NAT, b=
ut communication still does not work.<br>I would greatly appreciate any adv=
ice or suggestions on how to proceed.<br>Thank you for your time and suppor=
t.<br><br>Kind regards,<br>Daniele<br></div>

--00000000000056ea3406336e8c7c--