Help with routing between Windows

Guus Sliepen guus at tinc-vpn.org
Wed Sep 23 22:42:53 CEST 2009


On Wed, Sep 23, 2009 at 12:20:55PM -0700, Robert Spraggs wrote:

> I am having an issue with getting tinc to route the packets between
> 2 Windows tinc installations. Here is what I have so far:
> 
> homeClient: Physical Interface: 192.168.6.50 gateway 192.168.6.102
> homeClient: Tap-Win32 192.168.10.23 no gateway

What are the netmasks of those interfaces?

> vpnoffice: Physical Interface 192.168.6.102 gateway 192.168.6.1
> vpnoffice: Tap-Win32 192.168.98.10 no gateway
> 
> I run tinc -n vpn -d5 -D on both machines and I can see them connect
> and everything seems to go right, but nothing is being captured by
> tinc in the homeClient VMWare instance. I see minimal activity when
> I Wireshark the interface also.

The netmask of the TAP-Win32 interfaces should be 255.255.0.0 in your case. If
there is masquerading going on between the two machines, you might want to add
"TCPOnly = yes" to the host config files.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20090923/93960c94/attachment.pgp>


More information about the tinc mailing list