<br><br><div class="gmail_quote">On Fri, Jan 9, 2009 at 3:29 PM, Jean-Paul Calderone <span dir="ltr"><<a href="mailto:exarkun@divmod.com">exarkun@divmod.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, 9 Jan 2009 15:13:10 +0100, Alessio Pace <<a href="mailto:alessio.pace@gmail.com" target="_blank">alessio.pace@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Jan 9, 2009 at 3:01 PM, Alvin Delagon <<a href="mailto:adelagon@gmail.com" target="_blank">adelagon@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You shouldn't bind your client on a port where your server is listening to.<br>
</blockquote>
<br>
I'm following what is written in "Peer-to-Peer Communication Across Network<br>
Address Translators" in order to implement TCP hole punching, and they<br>
suggested to do so..<br>
</blockquote>
<br></div>
Are you talking about section 4.2? If so, try creating the client before<br>
you create the server. This is a somewhat arbitrary limitation imposed by<br>
your platform's implementation of the BSD socket API.</blockquote><div><br>Thanks for the suggestion, I'll try this and let you know.<br><br>Regards,<br>Alessio Pace.<br></div></div><br>