Re: issue with connecting two local peers

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

Hello,

Sorry for insisting so much! I just can not wait! I would love to use
gnunet! :)

Le sam. 14 d=C3=A9c. 2024 =C3=A0 21:16, gogo gogo <[email protected]> a =
=C3=A9crit :

> I really would love to see a configuration file example please!
>
>
> - for example for the socket, do you recommend:
> UNIXPATH =3D /tmp/gnunet-service-transport.sock
>
> but then for which peer(s)
>
> - I doubt for the second point
>
> - Could you tell me how please?
>
> - I am confused
>
> - I have already set http://localhost:8080/ . Should I do same for the se=
cond peers peer2.conf please?
>
>
> Le sam. 14 d=C3=A9c. 2024 =C3=A0 21:01, gogo gogo <[email protected]> =
a =C3=A9crit :
>
>> 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-m=
anually
>> 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 <maximedevos@telene=
t.be> a
>> =C3=A9crit :
>>
>>> 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
>>>
>>

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

<div dir=3D"ltr"><div>Hello,</div><div><br></div><div>Sorry for insisting s=
o much! I just can not wait! I would love to use gnunet! :)</div></div><br>=
<div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"=
gmail_attr">Le=C2=A0sam. 14 d=C3=A9c. 2024 =C3=A0=C2=A021:16, 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=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr"><pre>I really would love to see a configuration file exampl=
e please!<br></pre><pre><br>- for example for the socket, do you recommend:=
<br>UNIXPATH =3D /tmp/gnunet-service-transport.sock<br></pre><pre>but then =
for which peer(s)<br></pre><pre>- I doubt for the second point<br></pre><pr=
e>- Could you tell me how please?<br></pre><pre>- I am confused<br></pre><p=
re>- I have already set <a href=3D"http://localhost:8080/" target=3D"_blank=
">http://localhost:8080/</a> . Should I do same for the second peers peer2.=
conf please?</pre></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">Le=C2=A0sam. 14 d=C3=A9c. 2024 =C3=A0=C2=A021:01, gogo go=
go &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">gogo246475=
@gmail.com</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><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.org/latest/developers/tutorial.html#how-to-connect-=
manually" target=3D"_blank">https://docs.gnunet.org/latest/developers/tutor=
ial.html#how-to-connect-manually</a> and this is where I am stuck.</div><di=
v><br></div><div>Could you provide a configuration file example please?<br>=
</div></div><br><div class=3D"gmail_quote"><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:[email protected]" target=3D"_blank">maximedevos@telen=
et.be</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div><div lang=3D"NL-BE"><div><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 style=3D"margin-left:0cm">I=
f things are still the same as when I last worked with this (and IIRC), som=
e 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 getti=
ng confused from this.</li><li style=3D"margin-left:0cm">Maybe wait a few s=
econds 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 p=
ort yet? I=E2=80=99m not sure this is how it works though =E2=80=93 not fam=
iliar with this, this is speculation.</li><li 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 (uni=
directional), then the peers would be unable to verify each others existenc=
e.</li><li style=3D"margin-left:0cm">Even if they are choosen automatically=
, this automation probably had NAT-punching in mind, not this.</li><li styl=
e=3D"margin-left:0cm">For an isolated network, I think you also need to tel=
l 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"MsoNormal">=
It would be nice to have official documentation on setting up this kind iso=
lated one-machine, multiple peers network. It seems quite convenient for sa=
fely 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></div></div></blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000cc9ca806294184f2--