[tahoe-dev] Advertised invalid node port

[slush]

Hi Brian,

relaying transfers is last possible (and very traffic-expensive)
solution. Did you consider something like NAT punch [1]? Punching
isn't solution for every NAT setup, but when it is successful you
don't need any relay. In this case can Introducer play just role of
connection broker when both nodes are behind NAT.

And did you consider uPnP? I know that only small % of old home
routers have this feature, but most modern routers supports that by
default. Supporting both NAT punching and upnp (I think Twisted had
direct support for that) will significantly increase % of succesfully
connected NAT boxes.

[1] http://www.mindcontrol.org/~hplus/nat-punch.html

Marek

On Wed, Jun 16, 2010 at 7:33 PM, Brian Warner <warner at lothar.com> wrote:
> Incidentally, I'm slowly starting to work on the "Foolscap Relay
> Service", which would provide an easier-to-set-up but
> more-bandwidth-consuming solution to the NAT-bound-server problem. If I
> had relays, I'd probably use them instead of the pseudo-server trick.
>
> cheers,
>  -Brian