Hi Christian, I suppose the option you are saying to set are to be set in config file. My question is do I need to create a different file for each peer (which doesn't seem realistic if I have more no. of peers) or should I create a one config file with these options mentioned by you and other options will be used from default value. Will testbed-profiler take care of generating different config for each peer? And this config file has to passed as a argument in gnunet-testbed-profiler ? for example like this. $ *gnunet-testbed-profiler --config==template.conf --num-peers=2*
Thanks, Vikas On Sun, Feb 9, 2020 at 12:23 PM Christian Grothoff <[email protected]> wrote: > Hi Vikas, > > Your attempt to start two peers with the testbed driver worked. The > various warnings you are getting are related to specific configuration > issues (binaries not being SUID, old DSTJ-file lying around somewhere) > which you should be able to safely ignore. > > The only real issue is that you didn't give testbed any network > topology, so both of your peers are 'isolated' and don't talk to each > other. Try setting this option: > > [testbed] > OVERLAY_TOPOLOGY = CLIQUE > > (advice: don't use CLIQUE with > 200 peers!) and you should see the > peers connecting. Also, if you set > > [transport] > PLUGINS = unix > # (edit/remove existing option) > > some of the warnings/errors you are seeing should go away. > > Happy hacking! > > Christian > > On 2/8/20 8:23 PM, Vikas Maurya wrote: > > Hi, > > I have tried using two ways of setting up two peers on my system. first > > one from tutorial here > > > https://docs.gnunet.org/tutorial/gnunet-tutorial.html/Starting-Two-Peers-by-Hand.html#Starting-Two-Peers-by-Hand > > < > https://docs.gnunet.org/tutorial/gnunet-tutorial.html/Starting-Two-Peers-by-Hand.html#Starting-Two-Peers-by-Hand > >and > > second using *gnunet-testbed-profiler *with --num-peers=2. > > > > but in both the above methods I am facing problem with generating > > relevant configuration file to use. In profiler method I do not give any > > template configuration file (assuming it generates configuration file > > automatically for each peer, am I wrong?) I get the following errors, > > and I do not see any peers running when I issue *gnunet-core* command. > > > > <snip> > > 0 links succeeded > > 0 links failed due to timeouts > > Testbed running, waiting for keystroke to shut down > > Feb 08 19:58:49-763826 gnunet-daemon-topology-16815 WARNING `write' > > failed on file > > `/tmp/testbedsJXvfu/0/.config/gnunet//topology/friends.txt' at > > friends.c:82 with error: No such file or directory > > Feb 08 19:58:49-812577 vpn-16834 ERROR > > `/usr/local/lib//gnunet/libexec/gnunet-helper-vpn' is not SUID or the > > path is invalid, refusing to run. > > Feb 08 19:58:49-820170 gnunet-daemon-topology-16818 WARNING `write' > > failed on file > > `/tmp/testbedsJXvfu/1/.config/gnunet//topology/friends.txt' at > > friends.c:82 with error: No such file or directory > > Feb 08 19:58:49-843203 vpn-16829 ERROR > > `/usr/local/lib//gnunet/libexec/gnunet-helper-vpn' is not SUID or the > > path is invalid, refusing to run. > > Feb 08 19:58:50-014395 transport-tcp-16836 WARNING Unexpected address > > length: 24 bytes > > Feb 08 19:58:50-014474 transport-16836 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-014497 transport-16836 ERROR Address with 24 bytes for > > plugin tcp and peer DSTJ is malformed > > Feb 08 19:58:50-014518 transport-tcp-16836 WARNING Unexpected address > > length: 12 bytes > > Feb 08 19:58:50-014536 transport-16836 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-014553 transport-16836 ERROR Address with 12 bytes for > > plugin tcp and peer DSTJ is malformed > > Feb 08 19:58:50-015215 transport-tcp-16836 WARNING Unexpected address > > length: 24 bytes > > Feb 08 19:58:50-015245 transport-16836 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-015265 transport-16836 ERROR Address with 24 bytes for > > plugin tcp and peer V8XX is malformed > > Feb 08 19:58:50-015279 transport-tcp-16836 WARNING Unexpected address > > length: 12 bytes > > Feb 08 19:58:50-015292 transport-16836 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-015312 transport-16836 ERROR Address with 12 bytes for > > plugin tcp and peer V8XX is malformed > > Feb 08 19:58:50-021832 transport-tcp-16844 WARNING Unexpected address > > length: 24 bytes > > Feb 08 19:58:50-021910 transport-16844 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-021929 transport-16844 ERROR Address with 24 bytes for > > plugin tcp and peer DSTJ is malformed > > Feb 08 19:58:50-021954 transport-tcp-16844 WARNING Unexpected address > > length: 12 bytes > > Feb 08 19:58:50-021970 transport-16844 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-021991 transport-16844 ERROR Address with 12 bytes for > > plugin tcp and peer DSTJ is malformed > > Feb 08 19:58:50-022489 transport-tcp-16844 WARNING Unexpected address > > length: 24 bytes > > Feb 08 19:58:50-022508 transport-16844 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-022522 transport-16844 ERROR Address with 24 bytes for > > plugin tcp and peer V8XX is malformed > > Feb 08 19:58:50-022536 transport-tcp-16844 WARNING Unexpected address > > length: 12 bytes > > Feb 08 19:58:50-022547 transport-16844 ERROR Assertion failed at > > gnunet-service-transport_validation.c:902. > > Feb 08 19:58:50-022559 transport-16844 ERROR Address with 12 bytes for > > plugin tcp and peer V8XX is malformed > > Feb 08 19:58:59-920957 core-16825 WARNING Ignoring duplicate > > EPHEMERAL_KEY from Y924 > > Feb 08 19:58:59-947478 core-16831 WARNING Ignoring duplicate > > EPHEMERAL_KEY from Y924 > > Feb 08 19:59:00-186383 core-16825 WARNING Ignoring duplicate > > EPHEMERAL_KEY from FJMD > > Feb 08 19:59:00-201462 core-16831 WARNING Ignoring duplicate > > EPHEMERAL_KEY from FJMD > > <snip> > > > > My doubts are > > 1. how to use this *gnunet-testbed-profiler *correctly? > > 2. How to create config file for different peers on same system? (I > > tried using *gnunet-testing *for this but config files generated using > > this doesn't seem to work , which I tried using while following steps in > > tutorial mentioned above). > > 3. If I run multiple peers on a system How to check these peers are > > running correctly. > > > > > > Thanks, > > Vikas Maurya > > > > ** > > > > > >
