have the introducer advertise the external IP it sees for a node to other nodes #2152

New Issue

tahoe-lafs · 2014-01-15T15:10:17Z

daira commented

2014-01-15 15:10:17 +00:00

This might reduce the amount of manual configuration needed for tub.location, or work better in cases where a node's external IP is not stable.

It shouldn't introduce security problems because any connecting nodes will check via SSL that they are connecting to the right tubID.

We'd need to think about whether this IP should be added to the advertised location hints, or only be used by default if tub.location isn't configured, and/or when tub.location contains a special marker.

This might reduce the amount of manual configuration needed for `tub.location`, or work better in cases where a node's external IP is not stable. It shouldn't introduce security problems because any connecting nodes will check via SSL that they are connecting to the right tubID. We'd need to think about whether this IP should be added to the advertised location hints, or only be used by default if `tub.location` isn't configured, and/or when `tub.location` contains a special marker.

tahoe-lafs added the

labels 2014-01-15 15:10:17 +00:00

tahoe-lafs added this to the undecided milestone 2014-01-15 15:10:17 +00:00

daira commented

2014-01-15 16:04:44 +00:00

See also #50.

daira commented

2014-01-15 16:08:00 +00:00

If you like this ticket, you may also like #49 (UPnP), #169 (tcp hole-punching!), #445 (implement relay: allow storage servers behind NAT), and #754 (merge manually specified tub location with autodetected tub location).

Sign in to join this conversation.