Re: issue with connecting two local peers

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

I also suggest to add guideline to force dev to test and to make doc on
ANYTHING they create.

What do you all think of this idea please?

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

> 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=
=A9crit :
>
>> 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@pos=
teo.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 t=
o
>>> 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.). S=
o, 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 thi=
s, this is
>>>    speculation.
>>>    - I=E2=80=99m not sure if UDP ports are choosen automatically. If th=
ey
>>>    aren=E2=80=99t, then there might be some kind of port conflic. In ca=
se of UDP
>>>    (unidirectional), then the peers would be unable to verify each othe=
rs
>>>    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
>>>
>>>
>>>

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

<p dir=3D"ltr">I also suggest to add guideline to force dev to test and to =
make doc on ANYTHING they create.</p>
<p dir=3D"ltr">What do you all think of this idea 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:58, 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">I definitely wo=
uld like to use and maybe contribute to freenet</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le dim=
. 15 d=C3=A9c. 2024, 10:54, gogo gogo &lt;<a href=3D"mailto:gogo246475@gmai=
l.com" target=3D"_blank" rel=3D"noreferrer">[email protected]</a>&gt; a =
=C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">Co=
uld you either document the second method or can you give me the instructio=
n to do it manually 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]" rel=3D"noreferrer noreferrer" target=3D"_blank">mschanz=
[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"><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><di=
v>The first is to do it manually, by starting two peers with different conf=
igurations 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, t=
here 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:1=
2 +0100, Maxime 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 prob=
ably 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 t=
his (and IIRC), some things are _<i>outside</i>_ GNUNET_HOME. There are som=
e sockets =E2=80=A6 somewhere (I think under /tmp? Not sure where.). So, GN=
Unet 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, 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 thoug=
h =E2=80=93 not familiar with this, this is speculation.</li><li style=3D"m=
argin-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 (unidirectional), then the peers would be unable to verify eac=
h others existence.</li><li style=3D"margin-left:0cm">Even if they are choo=
sen automatically, this automation probably had NAT-punching in mind, not t=
his.</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 cla=
ss=3D"MsoNormal">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.)</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>
</blockquote></div>

--0000000000007062240629546bfc--