[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
network from scratch
From: |
accounts-gnunet |
Subject: |
network from scratch |
Date: |
Sun, 30 Oct 2022 12:37:34 +0000 |
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 makes p2p connection to A.
What happens instead:
A only gives B a single peer;
Y924NSHMMZ1N1SQCE5TXF93ED6S6JY311K0QT86G9WJC68F6XVZ0
---
Configuration excerpt:
[hostlist]
SERVERS =
OPTIONS = -p
[topology]
FRIENDS-ONLY = YES
FRIENDS = .../friends.txt
MINIMUM-FRIENDS = 1
# peer A
[hostlist]
SERVERS =
OPTIONS = -p
# peer B
[hostlist]
SERVERS = http://localhost:8080
#OPTIONS = -b
I tried feeding the output of gnunet-dht-hello into gnunet-dht-hello
<peer> on both peers, but it did not help. That was just a wild stab, and I
can't see
any other obvious likely ways of manually instructing a peer connection.
Three questions:
- how to explicitly connect to a known host?
- is it expected behavior that the peer running the hostlist should not
peer on information about itself? Shouldn't there at least be an
option for that?
- is it right that you always get peer
Y924NSHMMZ1N1SQCE5TXF93ED6S6JY311K0QT86G9WJC68F6XVZ0 no matter what?
thanks,
l
my_gnunet_bugreport.log
Description: Text document
signature.asc
Description: PGP signature
- network from scratch,
accounts-gnunet <=