On 01.11.22 14:58, t3sserakt wrote:
--
Message: 2
Date: Mon, 31 Oct 2022 15:45:15 +
From: accounts-gnu...@holbrook.no
To: Martin Schanzenbach
Cc: accounts-gnu...@holbrook.no, help-gnunet@gnu.org
Subject: Re: network from scratch
Message-ID:
Content-Type: text
--
Message: 2
Date: Mon, 31 Oct 2022 15:45:15 +
From: accounts-gnu...@holbrook.no
To: Martin Schanzenbach
Cc: accounts-gnu...@holbrook.no, help-gnunet@gnu.org
Subject: Re: network from scratch
Message-ID:
Content-Type: text/plain; charset=us-ascii
Aha so adding
15:45:15 +
From:accounts-gnu...@holbrook.no
To: Martin Schanzenbach
Cc:accounts-gnu...@holbrook.no,help-gnunet@gnu.org
Subject: Re: network from scratch
Message-ID:
Content-Type: text/plain; charset=us-ascii
Aha so adding -f to the gnunet-peer -s -g makes it output the hello.
And that URI is
2
> > > > Date: Mon, 31 Oct 2022 15:45:15 +
> > > > From:accounts-gnu...@holbrook.no
> > > > To: Martin Schanzenbach
> > > > Cc:accounts-gnu...@holbrook.no,help-gnunet@gnu.org
> > > > Subject: Re: network from scratch
> > > > M
:
--
Message: 2
Date: Mon, 31 Oct 2022 15:45:15 +
From:accounts-gnu...@holbrook.no
To: Martin Schanzenbach
Cc:accounts-gnu...@holbrook.no,help-gnunet@gnu.org
Subject: Re: network from scratch
Message-ID:
Content-Type: text/plain; charset=us-ascii
Aha so adding -f to the gnunet-peer -s -g makes
@gnu.org
Subject: Re: network from scratch
Message-ID:
Content-Type: text/plain; charset=us-ascii
Aha so adding -f to the gnunet-peer -s -g makes it output the hello.
And that URI is accepted by gnunet-peer -p
Now the peer is listed with gnunet-peer (-f)
Now peer A and B has both peer A and B in
lbrook.no,help-gnunet@gnu.org
> > Subject: Re: network from scratch
> > Message-ID:
> > Content-Type: text/plain; charset=us-ascii
> >
> > Aha so adding -f to the gnunet-peer -s -g makes it output the hello.
> >
> > And that URI is accepted by gnunet-peer -p
&
--
Message: 2
Date: Mon, 31 Oct 2022 15:45:15 +
From:accounts-gnu...@holbrook.no
To: Martin Schanzenbach
Cc:accounts-gnu...@holbrook.no,help-gnunet@gnu.org
Subject: Re: network from scratch
Message-ID:
Content-Type: text/plain; charset=us-ascii
Aha so adding -f
On 31.10.22 15:45, accounts-gnu...@holbrook.no wrote:
> Aha so adding -f to the gnunet-peer -s -g makes it output the hello.
>
> And that URI is accepted by gnunet-peer -p
>
> Now the peer is listed with gnunet-peer (-f)
>
> Now peer A and B has both peer A and B in their peerinfo lists.
>
> H
Aha so adding -f to the gnunet-peer -s -g makes it output the hello.
And that URI is accepted by gnunet-peer -p
Now the peer is listed with gnunet-peer (-f)
Now peer A and B has both peer A and B in their peerinfo lists.
However, the peer A is still not being sent by the hostlist (after retsta
Unfortunately, gnunet-peerinfo -s -g does not output the URI here, just
the same output as without -g.
I can get a gnunet:// scheme url using gnunet-dht-hello. However, if I
use that with gnunet-peerinfo -p I get:
Invalid URI
`gnunet://hello/ZV54JXNCQV9H7GJV603SQZJET1PPX3JKE94NCHNQZN81V1DQ5WJ0/R
On 30.10.22 12:37, accounts-gnu...@holbrook.no wrote:
> Following
> doc/handbook/html/users/configuration.html#configuring-the-friend-to-friend-f2f-mode,
> here's what I am trying to do:
>
> 1. Start peer A
> 2. Start peer B.
> 3. B connects to HTTP hostlist service, gets info for peer A.
> 4. B m
12 matches
Mail list logo
