Re: [tahoe-dev] Dynamic address
On Friday, September 13, 2013 13:35:28 Jerzy Łogiewa wrote: > If my Tahoe storage node IP change, I must update it in tracker manually? Is > there some way to automate it, to make storage node tell tracker new IP? I have some names pointing to my computer and these lines in tahoe.cfg: [node] tub.port = 14159 tub.location = bezitopo.org:14159 bezitopo.org is not a dynamic DNS name, I have to update it on the rare occasions that it changes, but if you have a DDNS name, it should update the introducer manually. My storage node is behind a firewall, so it doesn't know its external IP address. Pierre -- Jews use a lunisolar calendar; Muslims use a solely lunar calendar. ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] Dynamic address
Is some hashbased ident + discovery possible instead? Take for example the bittorrent sync. A secret look like: UF5O7G6XIMQKC7OH4J6NIPHDKVONMITO and that is all that is needed to find the share! -- Jerzy Łogiewa -- jerz...@interia.eu On Sep 15, 2013, at 3:24 PM, Pierre Abbat wrote: > On Friday, September 13, 2013 13:35:28 Jerzy Łogiewa wrote: >> If my Tahoe storage node IP change, I must update it in tracker manually? Is >> there some way to automate it, to make storage node tell tracker new IP? > > I have some names pointing to my computer and these lines in tahoe.cfg: > > [node] > tub.port = 14159 > tub.location = bezitopo.org:14159 > > bezitopo.org is not a dynamic DNS name, I have to update it on the rare > occasions that it changes, but if you have a DDNS name, it should update the > introducer manually. My storage node is behind a firewall, so it doesn't know > its external IP address. > > Pierre > -- > Jews use a lunisolar calendar; Muslims use a solely lunar calendar. > > ___ > tahoe-dev mailing list > tahoe-dev@tahoe-lafs.org > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] Dynamic address
I believe it has been suggested that the Introducer should "detect" incoming connections and thereby keep track of the addresses of connected nodes. If that was implemented you would only need to set the introducer furl and tub.port in your storage node config. The tub.port is of course needed for tahoe to know what port you have opened through your firewall for tahoe data traffic. Until that is implemented, we have a little script running on the storage nodes of out friendnet that automatically updates the node config file and restarts the node if the ipaddress changes. If you're on Linux you are welcome to try it. Regards, Anders 15 sep 2013 kl. 16:04 skrev Jerzy Łogiewa : > Is some hashbased ident + discovery possible instead? > > Take for example the bittorrent sync. A secret look like: > UF5O7G6XIMQKC7OH4J6NIPHDKVONMITO and that is all that is needed to find the > share! > > -- > Jerzy Łogiewa -- jerz...@interia.eu > > On Sep 15, 2013, at 3:24 PM, Pierre Abbat wrote: > >> On Friday, September 13, 2013 13:35:28 Jerzy Łogiewa wrote: >>> If my Tahoe storage node IP change, I must update it in tracker manually? Is >>> there some way to automate it, to make storage node tell tracker new IP? >> >> I have some names pointing to my computer and these lines in tahoe.cfg: >> >> [node] >> tub.port = 14159 >> tub.location = bezitopo.org:14159 >> >> bezitopo.org is not a dynamic DNS name, I have to update it on the rare >> occasions that it changes, but if you have a DDNS name, it should update the >> introducer manually. My storage node is behind a firewall, so it doesn't >> know >> its external IP address. >> >> Pierre >> -- >> Jews use a lunisolar calendar; Muslims use a solely lunar calendar. >> >> ___ >> tahoe-dev mailing list >> tahoe-dev@tahoe-lafs.org >> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev > > ___ > tahoe-dev mailing list > tahoe-dev@tahoe-lafs.org > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
