tinc - May 2010 - tinc confused on remote nodes behind NAT?

Something tells me this was covered recently, but i didn't find it again in
gmail.   The nodes see each other but if i have something misconfigured that
is decreasing my speed.

All my nodes are behind NATs.
i have a remote node that connects to a central node via port forwarding
from public port 7777 to hp821 running on port 655.

remoteNode ---->  public ip 1.2.3.4:7777  ---->  hp821:655

There are other nodes behind the central NAT that could be making outgoing
connections on port 655.

On Fri, May 21, 2010 at 10:32:38AM -0500, Rob Townley wrote:

[...]
> From the log below, the MTU port is different than the real port.  hp821
> seems to be seen on multiple ports, but i wonder if it is being confused
> with other nodes behind the same NAT.
[...]
> Got MTU probe length 1315 from hp821 (1.2.3.4 port 655)
MTU probe is done via UDP, so this log entry shows you the IP address and port
used for UDP.
> Sending PING to hp821 (1.2.3.4 port 7777): 8
PING and PONGs are sent via TCP, so this log entry shows you the IP address and
port used by the TCP connection. These port numbers are likely to differ, that
is not a problem.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20100521/f33c29f6/attachment.pgp>