<div dir="ltr">On Thu, Jan 31, 2013 at 3:08 AM, Leandro Dardini <span dir="ltr"><<a href="mailto:ldardini@gmail.com" target="_blank">ldardini@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span style="color:rgb(80,0,80)">2013/1/31 Ishfaq Malik </span><span dir="ltr" style="color:rgb(80,0,80)"><<a href="mailto:ish@pack-net.co.uk" target="_blank">ish@pack-net.co.uk</a>></span><br>
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 2013-01-30 at 14:10 -0700, Carlos Alvarez wrote:<br>
> On Wed, Jan 30, 2013 at 12:05 PM, XBrian <<a href="mailto:boboodz@yahoo.co.uk" target="_blank">boboodz@yahoo.co.uk</a>> wrote:<br>
> Thanks - I was hoping there was some silver bullet to use out<br>
> there. Thanks<br>
> anyway.<br>
></blockquote></div><div>If you have no NAT or dynamic IP in your network, you can just remove the registration process and assign to each peer its IP address.</div><span class="HOEnZb"><font color="#888888"><div><br>
</div></font></span></div></blockquote><div><br></div><div style>This is the answer. If 100% availability is critical, your IP addresses shouldn't be changing anyway, so take the registration process out entirely. </div>
</div><div><br></div>-- <br>-Chris Harrington<br><div>ACSDi Office: 763.559.5800</div><div><div>Mobile Phone: 612.326.4248</div></div><div><br></div>
</div></div>