You basically got it!<br><br>Yes you will be assigning additional IPs in the <a href="http://10.30.1.0/24">10.30.1.0/24</a> network for each computer that you want to participate in the VPN. <br><br>On the Tinc gateway PCs, if they're Windows machines, you'll be adding the additional IP to the bridge interface that you will create. In Windows, interfaces that are members of a bridge don't have any TCP/IP configuration, it's all done on the bridge itself. <br>
<br>Regards,<br>Donald<br><br><div class="gmail_quote">On Wed, Oct 6, 2010 at 9:26 PM, Andrew Savinykh <span dir="ltr"><<a href="mailto:andrews@brutsoft.com">andrews@brutsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Awesome! Now I think I finally understand how to do this. Thank you
very much. (Just to confirm, I need to assign the new additional IP
on physical adapter for each non tinc PC and on tap adapter for tinc
gateway PCs, right?)<br><font color="#888888">
<br>
Andrew.</font><div><div></div><div class="h5"><br>
<br>
On 7/10/2010 2:14 p.m., Donald Pearson wrote:
<blockquote type="cite">Sure it's possible, you just need to assign each node
a new IP in the <a href="http://10.30.1.0/24" target="_blank">10.30.1.0/24</a> network. It's not
part of the Tinc configuration, it's part of the network
configuration of each computer.<br>
<br>
All Tinc is doing, is creating a layer 2 path for them to reach
each other. Yes broadcasts will traverse the VPN. It literally
is virtual ethernet over the internet. :)<br></blockquote></div></div></div><br></blockquote></div><br>