[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] nat
From: |
Christian Grothoff |
Subject: |
Re: [GNUnet-developers] nat |
Date: |
Mon, 21 Jan 2019 12:29:16 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 |
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" 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?
- [GNUnet-developers] nat, Catonano, 2019/01/20
- Re: [GNUnet-developers] nat, Catonano, 2019/01/20
- Re: [GNUnet-developers] nat, Christian Grothoff, 2019/01/20
- Re: [GNUnet-developers] nat, Catonano, 2019/01/20
- Re: [GNUnet-developers] nat, Christian Grothoff, 2019/01/20
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21
- Re: [GNUnet-developers] nat,
Christian Grothoff <=
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21
- Re: [GNUnet-developers] nat, Christian Grothoff, 2019/01/21
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21
Re: [GNUnet-developers] nat, Kai A. Hiller, 2019/01/21
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21
- Re: [GNUnet-developers] nat, t3sserakt, 2019/01/21
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21
- Re: [GNUnet-developers] nat, Catonano, 2019/01/21