Re: issue with connecting two local peers

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

Could you either document the second method or can you give me the
instruction to do it manually please?

Le dim. 15 d=C3=A9c. 2024, 10:43, Martin Schanzenbach <mschanzenbach@posteo=
.de>
a =C3=A9crit :

> There are two ways of doing this in gnunet.
> The first is to do it manually, by starting two peers with different
> configurations and having them connect.
>
> But the proper way to do testing would be to use the (new) testing API.
> Alas, there is no usable documentation for either right now.
>
> BR
> Martin
>
> On Sat, 2024-12-14 at 18:12 +0100, Maxime Devos wrote:
>
> 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
>
>
>

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

<p dir=3D"ltr">Could you either document the second method or can you give =
me the instruction to do it manually please?</p>
<br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=
=3D"gmail_attr">Le dim. 15 d=C3=A9c. 2024, 10:43, Martin Schanzenbach &lt;<=
a href=3D"mailto:[email protected]">[email protected]</a>&gt; a=
 =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"NL-=
BE" link=3D"blue" vlink=3D"#954F72" style=3D"word-wrap:break-word"><div>The=
re are two ways of doing this in gnunet.</div><div>The first is to do it ma=
nually, by starting two peers with different configurations and having them=
 connect.</div><div><br></div><div>But the proper way to do testing would b=
e to use the (new) testing API.</div><div>Alas, there is no usable document=
ation for either right now.</div><div><br></div><div>BR</div><div>Martin</d=
iv><div><br></div><div>On Sat, 2024-12-14 at 18:12 +0100, Maxime Devos wrot=
e:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex;border-left:2p=
x #729fcf solid;padding-left:1ex"><div class=3D"m_3061199503145181624WordSe=
ction1"><p class=3D"MsoNormal">If you wish to start multiple peers on one m=
achine, 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"di=
sc"><li class=3D"m_3061199503145181624MsoListParagraph" style=3D"margin-lef=
t:0cm">If things are still the same as when I last worked with this (and II=
RC), 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_3061199503145181624MsoLi=
stParagraph" style=3D"margin-left:0cm">Maybe wait a few seconds after doing=
 =E2=80=98gnunet-arm [=E2=80=A6] -s=E2=80=99, instead of the &amp;&amp;. Ma=
ybe 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,=
 this is speculation.</li><li class=3D"m_3061199503145181624MsoListParagrap=
h" 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 por=
t conflic. In case of UDP (unidirectional), then the peers would be unable =
to verify each others existence.</li><li class=3D"m_3061199503145181624MsoL=
istParagraph" style=3D"margin-left:0cm">Even if they are choosen automatica=
lly, this automation probably had NAT-punching in mind, not this.</li><li c=
lass=3D"m_3061199503145181624MsoListParagraph" style=3D"margin-left:0cm">Fo=
r an isolated network, I think you also need to tell GNUnet to bind to =E2=
=80=98localhost=E2=80=99 instead of everything.</li></ul><p class=3D"MsoNor=
mal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal">It would be nice to hav=
e official documentation on setting up this kind isolated one-machine, mult=
iple 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 n=
eeded.)</p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNo=
rmal">Best regards,<br>Maxime Devos<u></u><u></u></p></div></blockquote><di=
v><br></div><div><span></span></div></div>
</blockquote></div>

--0000000000009dc87306294c0ed2--