<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Hi,<br><br>could this library not be used to solve the NAT Traversal problems? <br>http://www.pjsip.org/pjnath/docs/html/<br><br><div><span><br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Greg Troxel <gdt@ir.bbn.com><br> <b><span style="font-weight: bold;">To:</span></b> Anders Genell <anders.genell@gmail.com> <br><b><span style="font-weight: bold;">Cc:</span></b> "tahoe-dev@tahoe-lafs.org" <tahoe-dev@tahoe-lafs.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Saturday, July 13, 2013 1:38 AM<br> <b><span style="font-weight:
bold;">Subject:</span></b> Re: [tahoe-dev] Friendnet tub.location and tub.port<br> </font> </div> <div class="y_msg_container"><br><br>Anders Genell <<a ymailto="mailto:anders.genell@gmail.com" href="mailto:anders.genell@gmail.com">anders.genell@gmail.com</a>> writes:<br><br>> Right now we have uglyhacked a script to update the tahoe.cfg file and<br>> restart the node whenever the IP changes, by regularly checking<br>> e.g. myexternalip.com. Most nodes will run on Raspberry Pi hardware so<br>> a bash script is sufficient, but a bit of python should make it more<br>> platform independent, I suppose.<br><br>Presumably you mean to have the tahoe node figure out the public IP<br>address it is behind, and to be able to advertise that. That sounds<br>like the right approach for servers with deficient (NATed) IP<br>connectivity.<br><br>As an aside, it is bad form (gratuitously unportable) to write bash<br>scripts. Presumably
one could write a sh script, following POSIX sh<br>standards, and such a script could be properly executed by any<br>POSIX-compliant sh implemntation (bash, dash, NetBSD's /bin/sh, etc.).<br>(I'm not sure what you meant about not needing portability because of<br>Pi; note that NetBSD with it's own non-bash POSIX sh runs on the Pi<br>hardware, in addition to GNU/Linux. Presumably FreeBSD does as well.)<br><br>> My question is, should we need to set both tub.location and tub.port?<br>> Should we need to uglyhack to update IP alternatively use som dyndns<br>> equivalent? The introducer detects incoming IPs anyway, couldn't that<br>> be reported back to the node?<br><br>For now, I think you do. There's a pending discussion about having the<br>introducer use the IP address that it sees for the incoming connection.<br><br>_______________________________________________<br>tahoe-dev mailing list<br><a
ymailto="mailto:tahoe-dev@tahoe-lafs.org" href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br><a href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br><br><br></div> </div> </div> </div></body></html>