Re: issue with connecting two local peers

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

I definitely would like to use and maybe contribute to freenet

Le dim. 15 d=C3=A9c. 2024, 10:54, gogo gogo <[email protected]> a =C3=A9=
crit :

> 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@post=
eo.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=
, this is
>>    speculation.
>>    - I=E2=80=99m not sure if UDP ports are choosen automatically. If the=
y
>>    aren=E2=80=99t, then there might be some kind of port conflic. In cas=
e of UDP
>>    (unidirectional), then the peers would be unable to verify each other=
s
>>    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 =
for
>> safely testing things out. (Though for full isolation, a =E2=80=98unix=
=E2=80=99 transport
>> would be needed.)
>>
>>
>>
>> Best regards,
>> Maxime Devos
>>
>>
>>

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

<p dir=3D"ltr">I definitely would like to use and maybe contribute to freen=
et</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:54, gogo gogo &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"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">Could you eithe=
r document the second method or can you give me the instruction to do it ma=
nually please?</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le dim=
. 15 d=C3=A9c. 2024, 10:43, Martin Schanzenbach &lt;<a href=3D"mailto:mscha=
[email protected]" target=3D"_blank" rel=3D"noreferrer">mschanzenbach@post=
eo.de</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin: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>There are two ways of doing this in gnunet.</div><div>The first=
 is to do it manually, by starting two peers with different configurations =
and having them connect.</div><div><br></div><div>But the proper way to do =
testing would be to use the (new) testing API.</div><div>Alas, there is no =
usable documentation for either right now.</div><div><br></div><div>BR</div=
><div>Martin</div><div><br></div><div>On Sat, 2024-12-14 at 18:12 +0100, Ma=
xime Devos wrote:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex=
;border-left:2px #729fcf solid;padding-left:1ex"><div><p class=3D"MsoNormal=
">If you 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 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 style=3D"margin-left:0cm">Maybe wait a=
 few seconds after doing =E2=80=98gnunet-arm [=E2=80=A6] -s=E2=80=99, inste=
ad of the &amp;&amp;. Maybe the TCP or UDP transports haven=E2=80=99t choos=
en a port yet? I=E2=80=99m not sure this is how it works though =E2=80=93 n=
ot familiar with this, this is speculation.</li><li style=3D"margin-left:0c=
m">I=E2=80=99m not sure if UDP ports are choosen automatically. If they are=
n=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 exis=
tence.</li><li style=3D"margin-left:0cm">Even if they are choosen automatic=
ally, this automation probably had NAT-punching in mind, not this.</li><li =
style=3D"margin-left:0cm">For 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"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNorm=
al">It would be nice to have official documentation on setting up this kind=
 isolated one-machine, multiple peers network. It seems quite convenient fo=
r 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 Devos<u></u><u></u=
></p></div></blockquote><div><br></div><div><span></span></div></div>
</blockquote></div>
</blockquote></div>

--00000000000024f33e06294c1d02--