Re: [docs] patch: manually connecting peers

[Martin Schanzenbach]

Thanks applied!

On 07.11.22 08:06, accounts-gnunet@holbrook.no wrote:
> Hello,
> 
> Attached is a suggested patch for docs to describe how to manually connect
> peers and start a private network.
> 
> 
> best,
> l

> From 7ea4ea6d96443b20c7b22bc22d1e21a71893f659 Mon Sep 17 00:00:00 2001
> From: lash <dev@holbrook.no>
> Date: Wed, 2 Nov 2022 18:08:47 +0000
> Subject: [PATCH] Manually connecting peers, default hellos
> 
> Signed-off-by: lash <dev@holbrook.no>
> ---
>  users/configuration.rst | 45 +++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 45 insertions(+)
> 
> diff --git a/users/configuration.rst b/users/configuration.rst
> index 5cedfdc..2db37c3 100644
> --- a/users/configuration.rst
> +++ b/users/configuration.rst
> @@ -382,6 +382,7 @@ If you want to operate in normal P2P-only mode, simply set
>  ``MINIMUM-FRIENDS`` to zero and ``FRIENDS_ONLY`` to NO. This is the
>  default.
>  
> +
>  .. _Configuring-the-hostlist-to-bootstrap:
>  
>  Configuring the hostlist to bootstrap
> @@ -458,6 +459,50 @@ So your configuration file should include these lines:
>     SERVERS = http://v10.gnunet.org/hostlist [^]
>     HOSTLISTFILE = $SERVICEHOME/hostlists.file
>  
> +
> +.. _Disable_default_bootstrap:
> +
> +Disable default bootstrap (private network)
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +A public node will, by default, connect to a gnunet.org peer to learn
> +of other peers to bootstrap the network.
> +
> +To avoid this behavior, either:
> +
> +- before build, remove the peer entry in ``$REPO/contrib/hellos``
> +
> +- after build, remove the peer entry in ``$PREFIX/share/gnunet/hellos``
> +
> +Conversely, any public keys added to the same directories will make the
> +node *always* make explicit connections to those corresponding peers.
> +
> +
> +.. _Manually-connecting-peers:
> +
> +Manually connecting peers
> +~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +A gnunet node will learn peers to connect to from hostlist servers and/or
> +gossip from connected peers. It will however only connect to a selection
> +of peers on the network.
> +
> +If you wish to connect to a specific peer apart from the automatically
> +negotiated connections, you can use the ``hello`` URI of the peer. The
> +URI is returned by the following command to *peer to be connected to*:
> +
> +::
> +
> +   $ gnunet-peerinfo -s -g
> +
> +The URI output is passed to the ``gnunet-peerinfo`` command of *peer
> +that is connecting*:
> +
> +::
> +
> +   $ gnunet-peerinfo -s -p URI
> +
> +
>  .. _Configuration-of-the-HOSTLIST-proxy-settings-cli:
>  
>  Configuration of the HOSTLIST proxy settings
> -- 
> 2.38.0
>