Bridging on windows networks

Anon anon4321 at gmail.com
Mon Feb 1 10:20:22 CET 2010


>>* 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)
*
>Why don't you use the LAN IPs (same IPs) for the vpn, it will be much
>easier. Then you only have to set routing other computers in your lan via
>tinc computer. SOmetimes it is enouth to set the routing on your gateway.

I tried to do what you say and Windows complains when I try to set the TAP
interface to the same IP address as the one in use by the LAN IP interface.
Did you mean that I should set my vpn IP addresses as being on the same
192.168.x.0 set?  Hence, I would show the above as:

*192.168.0.155 (corresponds to 1.2.168.0.200)
**192.168.1.155 (corresponds to **1.2.168.1.200**)
**192.168.2.155 (corresponds to **1.2.168.2.200**)

If so, then I can change the DHCP server to only serve up through 199.

I'm not sure about how to set routing the way you are describing.  If you are
saying to set every other computer such that the Gateway is the tinc computer,
I don't think that will work for me, will it?  Maybe I'm not understanding
what you want me to do.


*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20100201/1503932a/attachment.htm>


More information about the tinc mailing list