[tahoe-dev] [tahoe-lafs-trac-stream] [tahoe-lafs] #1988: don't stop the process if you can't execute "ifconfig" or "route.exe"

[Paul Rabahy]

I was just about to suggest Greg's last point. I would move the "IP auto
discovery" out of the server and into the introducer. The local machine is
one of the worst reference points for getting your publicly visible IP (I
almost always think in a P2P, public grid way). I can see leaving an
override for privacy purposes, but there is nothing to stop the Introducer
from announcing the IP it sees anyway.

On Tue, Jun 25, 2013 at 10:50 PM, Greg Troxel <gdt at ir.bbn.com> wrote:

> I think removing autodetection of IP address would be a significant
> regression for people running storage nodes that might move.
>
> I think it would be good to figure out what is the problem really.   I
> don't understand why this is so hard.   The PATH issue makes me want to
> have configure-time finding of the right programs, based on OS, and then
> to invoke them with the configured path, period.
>
> Is anyone having an issue on BSD?  There, /sbin/ifconfig is quite
> stable.  So is the issue that various Linux flavors have withdrawn the
> previously-standard interfaces?
>
> An alternative would be to have the introducer look at the address that
> appears at it when the node connects, and use that to advertise, or
> perhaps just send it down the wire so the client can decide.
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130625/bbe83cc6/attachment.html>