Re: [Help-gnunet] Mar 13 11:21:44 WARNING: announcing ourselves pointless: no hosts known

[Christian Grothoff]

On Sunday 14 March 2004 14:45, David Roundy wrote:
> Hello.  I've been trying to get gnunet working on my debian testing box.  I
> installed the gnunet package (which is at version 0.6.1b), and edited the
> config files to set IP to my computer's external DNS name, and commented
> out both BLACKLISTs (I couldn't figure out how to get
> gnunet-transport-check to work otherwise).

gnunet-transport-check does not work with all network configurations anyway, 
in particular not with NAT.  I'm not sure what you mean by 'your computers 
external DNS name'.  Are you behind a NAT/Firewall or does your machine have 
multiple IP addresses (LAN+WAN?).  If there is a Firewall, I'll assume you 
poked a whole into it at port 2086 (and for NAT are forwarding it to the 
right machine in the LAN).

> I didn't seem to be able to connect, and saw a bunch of "no hosts known"
> errors in the log.  So I turned the debug level to EVERYTHING, and now I
> get following messages every minute or so:
>
> Mar 13 11:20:00 DEBUG: too few peers connected, waiting for 3048 to reach
> 4096 before trying HTTP download (again). Mar 13 11:20:15 DEBUG: too few
> peers connected, waiting for 3049 to reach 4096 before trying HTTP download
> (again). Mar 13 11:20:31 DEBUG: too few peers connected, waiting for 3050
> to reach 4096 before trying HTTP download (again). Mar 13 11:20:47 DEBUG:
> too few peers connected, waiting for 3051 to reach 4096 before trying HTTP
> download (again). Mar 13 11:20:50 CRON: enter cronRefreshAddress
> Mar 13 11:20:50 CRON: exit cronRefreshAddress
> Mar 13 11:21:03 DEBUG: too few peers connected, waiting for 3052 to reach
> 4096 before trying HTTP download (again). Mar 13 11:21:19 DEBUG: too few
> peers connected, waiting for 3053 to reach 4096 before trying HTTP download
> (again). Mar 13 11:21:34 DEBUG: too few peers connected, waiting for 3054
> to reach 4096 before trying HTTP download (again). Mar 13 11:21:44 WARNING:
> announcing ourselves pointless: no hosts known Mar 13 11:21:44 WARNING:
> announcing ourselves pointless: no hosts known Mar 13 11:21:44 WARNING:
> announcing ourselves pointless: no hosts known

What does gnunet-stats say? I'd suspect you have 0 connected hosts and are not 
receiving anything.  A first easy workaround might be to just configure 
limited NAT (only load NAT transport and set LIMITED to YES).  Then wait a 
while and check if your peer connects using gnunet-stats.  If so, turn 
limited off again, add TCP/UDP back as transports and check if traffic from 
the outside can actually reach the local port.

> I figure I've probably made a mistake somewhere, but am not clear where.
> "gnunet-search GPL" just waits there for a long time.
>
> Any idea as to what might be going wrong?

Sounds like a network configuration problem (firewall, NAT, wrong IP, etc.).  
Should not be too difficult to fix :-).

Christian