Re: [Help-gnunet] NAT clarification

[Christian Grothoff]

On Thursday 10 Jun 2004 5:55 am, Brent Miller wrote:
> from contrib/gnunet.root under the [NAT] section:
> > Set this only to YES if other peers
> > can not contact you directly via TCP or UDP.
> > If you set this to NO, you should also set the
> > TCP and UDP port to '0' to indicate that you
> > can not accept inbound connections.
>
> Shouldn't that read "If you set this to YES, you should also set the
> TCP and UDP port to '0'..."?

Right.  Fixed in CVS.

> If I am *not* NAT'ed (or can forward the appropriate ports), I would set
> "LIMITED = NO", right? So why would I set my TCP and UDP ports to 0 to
> indicate that I cannot accept connections when I can? Is this a typo, or
> am I misunderstanding something?

Typo.

> Also, if I set the UDP port to 0, (LIMITED = YES or NO) gnunetd tells me:
> Jun  9 16:45:20 Cannot determine port to bind to.  Define in
> configuration file
> in section UDP under PORT or in /etc/services under udp/gnunet.
> Jun  9 16:45:20 __BREAK__ at logging.c:241
>
> Should I just disable udp if I'm stuck behind a NAT?

Right.  I've fixed that in the docs to.  To summarize:

Behind nat:
LIMITED = YES
TCP-PORT = 0,
UDP: disable transport

Normal:
LIMITED = NO
TCP-PORT = 2086 (or other non-0-value)
UDP: can be used

> Thanks,
> Brent

Thanks for pointing out the bad docs.

Christian