Thanks for the swift reply. I appreciate it!<br><br>I'll give it another shot, although i'm sure that's how I had it setup, but the server kept saying it didn't know how to get to the client, because the clients host file on the server doesn't contain an address for the host (Because the client address is dynamic).<br>
<br>Also, how could I circumvent the nat problem? With a simple port opening of TCP/UDP 655 wherever the clients are (if they can)?<br><br>Could you post an example tinc.conf for the server and one of the clients for me so I can see what I got matches what you got, based on my previous email? Maybe a host file for each too so I can see how thats done?<br>
<br>My previous testing got me connected to each other but I had to manually have the external IPs of each client setup in each host... but as the only machine that doesn't change address is the server, its not very flexible or convenient.<br>
<br>I must also note that the server will be running Ubuntu Server 9.04 (Tinc version 1.0.9) and some of the clients will be linux and some will be Windows. For the moment though, its all Linux on Linux action. I assume Tinc doesn't care as long as the host files and tinc.confs are setup ok?<br>
<br>Regards,<br><br>Andy Barlow<br><br><br><br><div class="gmail_quote">2009/3/4 Guus Sliepen <span dir="ltr"><<a href="mailto:guus@tinc-vpn.org">guus@tinc-vpn.org</a>></span><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="im">On Wed, Mar 04, 2009 at 12:56:46PM +0000, Andrew Barlow wrote:<br>
<br>
> I have tried for days on end with no success on this, so I thought I would<br>
> post it here and see if someone can help me at all.<br>
><br>
</div>> *Here's the scenario:*<br>
><br>
[1 server, multiple clients with changing IP addresses]<br>
<div class="im">><br>
> I assumed you would only need to have inside each client host file something<br>
> like:<br>
><br>
> "ConnectTo = server<br>
> *KeyStuff*"<br>
><br>
> And the server would do the rest for me perhaps?<br>
<br>
</div>Yes, that's basically the only thing you need with tinc. The only possible<br>
problem is with NAT. Tinc has no support (yet) to penetrate NATs, so clients<br>
behind a NAT will have problems talking to each other directly.<br>
<font color="#888888"><br>
--<br>
Met vriendelijke groet / with kind regards,<br>
Guus Sliepen <<a href="mailto:guus@tinc-vpn.org">guus@tinc-vpn.org</a>><br>
</font><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
iEYEARECAAYFAkmuktgACgkQAxLow12M2ntZhgCgl/yxR3VhcuFPyt+QtXDSCFpf<br>
J+4AoK1em6gLAKx3dEyTLZ4f36cJe7Yx<br>
=xYmC<br>
-----END PGP SIGNATURE-----<br>
<br>_______________________________________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br>
<a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" target="_blank">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br>
<br></blockquote></div><br>