On 1/21/19 1:00 PM, Catonano wrote: > > > Il giorno lun 21 gen 2019 alle ore 12:29 Christian Grothoff > <[email protected] <mailto:[email protected]>> ha scritto: > > On 1/21/19 9:02 AM, Catonano wrote: > > > > Is there anything I can do ? Can I change the line that Gnunet uses ? > > Well, that's the interesting thing here: your original settings worked > with "upnpc -a LOCAL-IP PORT PORT tcp" yielding "external > 151.45.41.58:2086 <http://151.45.41.58:2086>" as the line in the > output we should look for. > > You found a way to change the setting to make our existing "-r" option > work, but that's not something _most_ users we hope to eventually have > will ever do. So we should modify src/nat/gnunet-service-nat_mini.c to > automatically try *both* methods. > > This would ideally be done by someone who has a NAT that behaves in > exactly this way. Anyone here able and willing to help out? > > > that would make me a potential candidate ;-) > > Too bad I didn't touch a single line of C code in my life > > My offer: someone else writes the code, they push it in a branch and I > can test that branch
Thanks for the offer, that's a first important step ;-) > I could appreciate some instructions about how to run gnunet from the > build folder, without instaling it That I can answer quickly: you cannot. _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
