Bridging on windows networks

[Anon]

Many thanks for the help to date.  I now have a working vpn with three
nodes:

10.20.30.1
10.20.40.1
10.20.50.1

Each machine can see each other machine 100's of miles apart from each
other.

Each machine is behind its own router.  The machines are on their own
subnets, as well, of course.  The individual IP's on the lans of the nodes
are:

192.168.0.155 (corresponds to 10.20.30.1)
192.168.1.155 (corresponds to 10.20.40.1)
192.168.2.155 (corresponds to 10.20.50.1)

I have another computer on the 192.168.0.x LAN, with IP address
192.168.0.188.  192.168.0.188 can ping 192.168.0.155 with no problem (and
vice versa).  But it can't ping 10.20.30.1 (or any of the others).

So, I either need to install a TAP interface on 192.168.0.188 and give it an
IP address of something like 10.20.60.1 and then run tinc on it (thereby
treating it as a new node on the vpn - I've tried this, and it seems to
work) or I need to bridge the 192.168.0.x LAN to the 10.20.30.1 node.

The problem is that I don't want to do the first option (configure each
machine as a tinc node) and I'm therefore hopeful that bridging is less
difficult to maintain. Of course, I don't know how to accomplish the second
option (bridge the LAN to the vpn).  Is it supposed to be as simple as
selecting both network connections in Network Connections on the
192.168.0.155 (10.20.30.1) machine, right clicking and selecting "Bridge
Connections"?  I tried that and the IP address of the bridged connection was
a new DHCP address (192.168.0.175) and it could no longer ping the vpn.  So
I didn't try to ping 10.20.30.1 from 192.168.0.188.

Am I missing something simple? (I hope so)

Thanks again.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20100131/6a146a5d/attachment.htm>