<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Donald,<br>
<br>
Excellent! 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>
<br>
Andrew<br>
PS. for some reason not all my messages reach the list, so I'm
resubmitting this one in hope that it's show up.<br>
I sent another message thanking Alan for his suggestion as it
totally makes sense to me. the only thing with that suggestion is
that broadcasts won't be possible.<br>
That message didn't show up either.<br>
<br>
<blockquote cite="mid:4CAD21E0.1020501@brutsoft.com" type="cite"> On
7/10/2010 2:14 p.m., Donald Pearson wrote:
<blockquote
cite="mid:AANLkTi=_rSo3rtOpv6OgQfY-7XQDqBw1KNnWv2Fqk+Da@mail.gmail.com"
type="cite">Sure it's possible, you just need to assign each
node a new IP in the <a moz-do-not-send="true"
href="http://10.30.1.0/24">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>
<br>
<div class="gmail_quote">On Wed, Oct 6, 2010 at 9:04 PM, Andrew
Savinykh <span dir="ltr"><<a moz-do-not-send="true"
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"> Donald, thank you for
this. <br>
<br>
Do i read you right that to be able to receive broadcasts
across LANs I have to use the address space that I already
have and make sure that this space is the same for both
LANs?<br>
<br>
What I'm trying to do is to define a *completely new
subnet* that will act as the common LAN foR both LAN A and
LAN B.<br>
<br>
To re-iterate:<br>
I have one router that is 10.1.1.1 and gives out DHCP
10.1.1.* and the other router 192.168.0.1 that gives out
DHCP 192.168.0.*. <br>
I would like to leave these address spaces alone and
define a new on 10.30.1.* that computer from both networks
can participate in effectively forming a new virtual LAN.<br>
<br>
Is this possible with tinc? I know this possible with
other software, I'm just having hard time figuring out if
this is something I can configure tinc to do.<br>
<font color="#888888"> <br>
Andrew</font><br>
</div>
</blockquote>
</div>
</blockquote>
</blockquote>
<br>
</body>
</html>