two tinc hosts behind same NAT
Eric Feliksik
feliksik at gmail.com
Fri Dec 5 12:26:04 CET 2014
Dear all,
I have 3 nodes: A, B and C. C has external IP and A and B are behind NAT.
It turns out A and B route their traffic via the C, which they ConnectTo
with; this instead of getting connection details from one another and
contacting eachother directly (mesh style). The reason is, as I conclude
from tincd debug output, is that they see the peer as having a minimum MTU
of 0. I suspect this is because both nodes happen to be behind the same NAT
and thus have the same public IP, in this particular case.
If I place the nodes in different NATed enviroments (different public IP's)
it does work.
Can this be fixed in a way such that nodes A and B do directly communicate?
Thanks in advance,
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20141205/26242f85/attachment.html>
More information about the tinc
mailing list