This is the way I understand it. All nodes become aware of all other nodes. As long as one node can connect to another, you'll get a client to client connection.
If 2 clients are both behind blocking firewalls, neither will be able to directly connect to the other without one of them having a port open. In that situation their traffic will need to route through another node. On Mon, Jun 8, 2015 at 12:55 PM, Cristiano Albiero Berni < [email protected]> wrote: > Hi, > I have some questions about tinc. > > " > *Automatic full mesh routing*Regardless of how you set up the tinc > daemons to connect to each other, VPN traffic is always (if possible) sent > directly to the destination, without going through intermediate hops. > " > > 1- To have client to client direct connection and don't have traffic > through the server should I have port forward at the NAT? Or a client to > client tunnel can be build ignoring the NAT rules? > > 2- Is there a kind of web interface to manager the server? > > 3- Any release date of tinc 2.0 version? > > > > Kind regards, > Cristiano. > animati.com.br > > > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > >
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
