Re: issue with connecting two local peers

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

Hi maxime,

I think there is already an official doc I was referring to
https://docs.gnunet.org/latest/developers/tutorial.html#how-to-connect-manu=
ally
and this is where I am stuck.

Could you provide a configuration file example please?

Le sam. 14 d=C3=A9c. 2024 =C3=A0 18:12, Maxime Devos <[email protected]=
e> a
=C3=A9crit :

> If you wish to start multiple peers on one machine, you probably need to
> adjust the configuration more.
>
>
>
>    - If things are still the same as when I last worked with this (and
>    IIRC), some things are _*outside*_ GNUNET_HOME. There are some sockets
>    =E2=80=A6 somewhere (I think under /tmp? Not sure where.). So, GNUnet =
might be
>    getting confused from this.
>    - Maybe wait a few seconds after doing =E2=80=98gnunet-arm [=E2=80=A6]=
 -s=E2=80=99, instead of
>    the &&. Maybe the TCP or UDP transports haven=E2=80=99t choosen a port=
 yet? I=E2=80=99m not
>    sure this is how it works though =E2=80=93 not familiar with this, thi=
s is
>    speculation.
>    - I=E2=80=99m not sure if UDP ports are choosen automatically. If they=
 aren=E2=80=99t,
>    then there might be some kind of port conflic. In case of UDP
>    (unidirectional), then the peers would be unable to verify each others
>    existence.
>    - Even if they are choosen automatically, this automation probably had
>    NAT-punching in mind, not this.
>    - For an isolated network, I think you also need to tell GNUnet to
>    bind to =E2=80=98localhost=E2=80=99 instead of everything.
>
>
>
> It would be nice to have official documentation on setting up this kind
> isolated one-machine, multiple peers network. It seems quite convenient f=
or
> safely testing things out. (Though for full isolation, a =E2=80=98unix=E2=
=80=99 transport
> would be needed.)
>
>
>
> Best regards,
> Maxime Devos
>

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

<div dir=3D"ltr"><div>Hi maxime,</div><div><br></div><div>I think there is =
already an official doc I was referring to <a href=3D"https://docs.gnunet.o=
rg/latest/developers/tutorial.html#how-to-connect-manually">https://docs.gn=
unet.org/latest/developers/tutorial.html#how-to-connect-manually</a> and th=
is is where I am stuck.</div><div><br></div><div>Could you provide a config=
uration file example please?<br></div></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0sam. 14=
 d=C3=A9c. 2024 =C3=A0=C2=A018:12, Maxime Devos &lt;<a href=3D"mailto:maxim=
[email protected]">[email protected]</a>&gt; a =C3=A9crit=C2=A0:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"msg8561=
859790472967154"><div lang=3D"NL-BE" style=3D"overflow-wrap: break-word;"><=
div class=3D"m_8561859790472967154WordSection1"><p class=3D"MsoNormal">If y=
ou wish to start multiple peers on one machine, you probably need to adjust=
 the configuration more. </p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p=
><ul style=3D"margin-top:0cm" type=3D"disc"><li class=3D"m_8561859790472967=
154MsoListParagraph" style=3D"margin-left:0cm">If things are still the same=
 as when I last worked with this (and IIRC), some things are _<i>outside</i=
>_ GNUNET_HOME. There are some sockets =E2=80=A6 somewhere (I think under /=
tmp? Not sure where.). So, GNUnet might be getting confused from this.</li>=
<li class=3D"m_8561859790472967154MsoListParagraph" style=3D"margin-left:0c=
m">Maybe wait a few seconds after doing =E2=80=98gnunet-arm [=E2=80=A6] -s=
=E2=80=99, instead of the &amp;&amp;. Maybe the TCP or UDP transports haven=
=E2=80=99t choosen a port yet? I=E2=80=99m not sure this is how it works th=
ough =E2=80=93 not familiar with this, this is speculation.</li><li class=
=3D"m_8561859790472967154MsoListParagraph" style=3D"margin-left:0cm">I=E2=
=80=99m not sure if UDP ports are choosen automatically. If they aren=E2=80=
=99t, then there might be some kind of port conflic. In case of UDP (unidir=
ectional), then the peers would be unable to verify each others existence.<=
/li><li class=3D"m_8561859790472967154MsoListParagraph" style=3D"margin-lef=
t:0cm">Even if they are choosen automatically, this automation probably had=
 NAT-punching in mind, not this.</li><li class=3D"m_8561859790472967154MsoL=
istParagraph" style=3D"margin-left:0cm">For an isolated network, I think yo=
u also need to tell GNUnet to bind to =E2=80=98localhost=E2=80=99 instead o=
f everything.</li></ul><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p cl=
ass=3D"MsoNormal">It would be nice to have official documentation on settin=
g up this kind isolated one-machine, multiple peers network. It seems quite=
 convenient for safely testing things out. (Though for full isolation, a =
=E2=80=98unix=E2=80=99 transport would be needed.)</p><p class=3D"MsoNormal=
"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal">Best regards,<br>Maxime De=
vos<u></u><u></u></p></div></div></div></blockquote></div>

--00000000000060cd0c062940691b--