[tahoe-dev] Friendnet tub.location and tub.port

[Greg Troxel]

Anders Genell <anders.genell at gmail.com> writes:

> Right now we have uglyhacked a script to update the tahoe.cfg file and
> restart the node whenever the IP changes, by regularly checking
> e.g. myexternalip.com. Most nodes will run on Raspberry Pi hardware so
> a bash script is sufficient, but a bit of python should make it more
> platform independent, I suppose.

Presumably you mean to have the tahoe node figure out the public IP
address it is behind, and to be able to advertise that.  That sounds
like the right approach for servers with deficient (NATed) IP
connectivity.

As an aside, it is bad form (gratuitously unportable) to write bash
scripts.  Presumably one could write a sh script, following POSIX sh
standards, and such a script could be properly executed by any
POSIX-compliant sh implemntation (bash, dash, NetBSD's /bin/sh, etc.).
(I'm not sure what you meant about not needing portability because of
Pi; note that NetBSD with it's own non-bash POSIX sh runs on the Pi
hardware, in addition to GNU/Linux.  Presumably FreeBSD does as well.)

> My question is, should we need to set both tub.location and tub.port?
> Should we need to uglyhack to update IP alternatively use som dyndns
> equivalent?  The introducer detects incoming IPs anyway, couldn't that
> be reported back to the node?

For now, I think you do.  There's a pending discussion about having the
introducer use the IP address that it sees for the incoming connection.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130712/7c60849b/attachment.pgp>