[tahoe-dev] Troubleshooting node connectivity

[Shawn Willden]

On Wednesday 09 September 2009 01:17:18 am Brian Warner wrote:
> The storage-server hostname/port that's advertised in the Introducer
> announcement (tahoe.cfg:[node]tub.location) needs to be able to get
> through to the port number that the server is actually listening on
> (tahoe.cfg:[node]tub.port).

Got it.  Looking at the flogtool output it became immediately clear that the 
firewalled/NATed hosts were announcing their local IP address.  The ports 
were forwarded correctly, but they were announcing non-useful IP addresses.

I wonder if it might be better to have the introducer tell the node what IP 
address it receives the connection from, and to have the node use that as its 
guessed address, if no explicit address has been configured.  The hosts in 
questions are on dynamic IP addresses, so in theory it's hard to configure 
the proper tub.location.  In theory, I say, because the dynamic addresses in 
question hardly ever change.

Using the node's address as seen by the introducer will make configuration of 
a NATed node much simpler for non-technical users, who may not even have any 
idea how to find out what their external IP address is.

	Shawn.