Could you either document the second method or can you give me the instruction to do it manually please?
Le dim. 15 déc. 2024, 10:43, Martin Schanzenbach <mschanzenb...@posteo.de> a écrit : > There are two ways of doing this in gnunet. > The first is to do it manually, by starting two peers with different > configurations and having them connect. > > But the proper way to do testing would be to use the (new) testing API. > Alas, there is no usable documentation for either right now. > > BR > Martin > > On Sat, 2024-12-14 at 18:12 +0100, Maxime Devos wrote: > > If you wish to start multiple peers on one machine, you probably need to > 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 > … somewhere (I think under /tmp? Not sure where.). So, GNUnet might be > getting confused from this. > - Maybe wait a few seconds after doing ‘gnunet-arm […] -s’, instead of > the &&. Maybe the TCP or UDP transports haven’t choosen a port yet? I’m not > sure this is how it works though – not familiar with this, this is > speculation. > - I’m not sure if UDP ports are choosen automatically. If they aren’t, > then there might be some kind of port conflic. In case of UDP > (unidirectional), then the peers would be unable to verify each others > 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 ‘localhost’ 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 ‘unix’ transport > would be needed.) > > > > Best regards, > Maxime Devos > > >
