<!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">
I tried the configuration below and I get the following error on
homeClient<br>
Cannot route packet from homeClient (MYSELF): unknown ipv4 destination
address 10.10.255.255<br>
<br>
I get the following error on vpnoffice<br>
Cannot route packet from vpnoffice (MYSELF): unknown ipv4 destination
address 10.5.255.255<br>
<br>
Thanks<br>
<br>
Robert<br>
<br>
Guus Sliepen wrote:
<blockquote cite="mid:20090925183013.GV4452@sliepen.org" type="cite">
<pre wrap="">On Fri, Sep 25, 2009 at 09:24:41AM -0700, Robert Spraggs wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks everyone for the help, but I think I need to restart this
process. I am trying to blend too many suggestions into a solution and
I don't think it's working. Here is the configuration that I have setup:
</pre>
</blockquote>
<pre wrap=""><!---->[...]
</pre>
<blockquote type="cite">
<pre wrap="">////=============================================/////
homeClient:
IP: 192.168.6.50 netmask: 255.255.255.0 gw 192.168.6.1
TAP-Win32: 10.10.10.10 netmask 255.0.0.0
Subnet=10.10.10.10/32
Address=192.168.6.50
TCPonly=yes
</pre>
</blockquote>
<pre wrap=""><!---->[...]
</pre>
<blockquote type="cite">
<pre wrap="">////==============================================/////
vpnoffice
IP 192.168.2.102 netmask 255.255.255.0 gw 192.168.2.2
TAP-Win32: 10.5.10.10.10 netmask 255.0.0.0
Subnet=10.5.10.10/32
Address=192.168.2.102
TCPonly=yes
</pre>
</blockquote>
<pre wrap=""><!---->[...]
</pre>
<blockquote type="cite">
<pre wrap="">Without Tinc running I am able to ping 192.168.2.254 from the
homeClient machine. When I have tinc started, I can still ping
192.168.2.254, but I don't think that the TAP-Win32 interface is
capturing the packets, because nothing shows up in the wireshark log.
</pre>
</blockquote>
<pre wrap=""><!---->
With the above configuration, tinc only knows about 10.10.10.10 and 10.5.10.10.
You also told Windows that only packets to 10.0.0.0/8 should go via the VPN,
the rest still goes via your real network interface. You should be able to ping
10.5.10.10 from 10.10.10.10, and vice versa.
If you want to be able to ping 192.168.* addresses via the VPN, you must let
tinc use those addresses:
Try changing the configuration of the TAP-Win32 adapter of homeClient to
192.168.6.50 netmask 255.255.0.0, and that of vpnoffice to 192.168.2.102
netmask 255.255.0.0. Replace Subnet=10.10.10.10/32 with Subnet=192.168.6.0/24,
and Subnet=10.5.10.10/32 with Subnet=192.168.2.0/24.
</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
tinc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a>
<a class="moz-txt-link-freetext" href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a>
</pre>
<pre wrap="">
<hr size="4" width="90%">
No virus found in this incoming message.
Checked by AVG - <a class="moz-txt-link-abbreviated" href="http://www.avg.com">www.avg.com</a>
Version: 8.5.409 / Virus Database: 270.13.112/2394 - Release Date: 09/25/09 05:51:00
</pre>
</blockquote>
</body>
</html>