Are you using DHCP on these hosts or something?<br><br>Look at the route tables again. 168 has a route to use 155 as it's gateway for the <a href="http://10.20.0.0/16">10.20.0.0/16</a> network, which as you describe the scene, is correct.<br>
<br>But, looking at the route table for the tinc node, it's ip address is 115, *not* 155.<br><br><div class="gmail_quote">On Fri, Feb 5, 2010 at 5:06 PM, Anon <span dir="ltr"><<a href="mailto:anon4321@gmail.com">anon4321@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Well, I'm back. I'm still trying to get a simple ping from a<br>
non-tinc-node on a LAN to a tinc node on that same LAN. (I'm taking<br>
baby steps.)<br>
<br>
I'll reprint the route prints below.<br>
<br>
To recap, tinc is running on 192.168.0.155, with a corresponding vpn<br>
address of 10.20.30.1. This machine can ping 192.168.0.168 with no<br>
problem. This machine can ping two offsite vpn nodes with no problem:<br>
10.20.40.1 and 10.20.50.1. And they can, in turn, ping 10.20.30.1.<br>
<br>
192.168.0.168 can ping 192.168.0.155 with no problem.<br>
<br>
192.168.0.168 can not ping 10.20.30.1. This is the problem I'm trying<br>
to address. My goal, of course, is to allow all the computers on<br>
192.168.0.x to ping 10.20.30.1 (and 10.20.40.1 and 10.20.50.1), not<br>
just 192.168.0.168.<br>
<br>
I previously posted the route prints from 192.168.0.155 and 192.168.0.168.<br>
<br>
I was told to add a static route to 192.168.0.168 as follows:<br>
<br>
route add 10.20.0.0 MASK 255.255.0.0 192.168.0.155<br>
<br>
Tinc is NOT running on 192.168.0.168.<br>
<br>
On the hosts file for 192.168.0.155 (called myserv), the subnet used to be:<br>
<br>
Subnet = <a href="http://10.20.30.1/32" target="_blank">10.20.30.1/32</a><br>
<br>
I have now added the following line right below the above:<br>
<br>
Subnet = <a href="http://192.168.0.0/24" target="_blank">192.168.0.0/24</a><br>
<br>
The only thing I'm trying to accomplish at the moment is to ping<br>
10.20.30.1 from 192.168.0.168.<br>
<br>
If anybody can suggest a step I'm missing, I'd be appreciative.<br>
<br>
192.168.0.168<br>
<br>
===========================================================================<br>
Interface List<br>
0x1 ........................... MS TCP Loopback interface<br>
0x3 ...00 21 5c 59 d2 83 ...... Intel(R) Wireless WiFi Link 4965AGN -<br>
Packet Scheduler Miniport<br>
===========================================================================<br>
===========================================================================<br>
Active Routes:<br>
Network Destination Netmask Gateway Interface Metric<br>
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.168 25<br>
10.20.0.0 255.255.0.0 192.168.0.155 192.168.0.168 1<br>
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1<br>
192.168.123.0 255.255.255.0 192.168.0.168 192.168.0.168 25<br>
192.168.0.168 255.255.255.255 127.0.0.1 127.0.0.1 25<br>
192.168.123.255 255.255.255.255 192.168.0.168 192.168.0.168 25<br>
224.0.0.0 240.0.0.0 192.168.0.168 192.168.0.168 25<br>
255.255.255.255 255.255.255.255 192.168.0.168 192.168.0.168 1<br>
255.255.255.255 255.255.255.255 192.168.0.168 2 1<br>
255.255.255.255 255.255.255.255 192.168.0.168 10006 1<br>
255.255.255.255 255.255.255.255 192.168.0.168 20004 1<br>
Default Gateway: 192.168.0.1<br>
===========================================================================<br>
Persistent Routes:<br>
None<br>
<br>
<a href="http://10.20.30.1/192.168.0.155" target="_blank">10.20.30.1/192.168.0.155</a><br>
<br>
===========================================================================<br>
Interface List<br>
0x1 ........................... MS TCP Loopback interface<br>
0x6 ...00 1a a0 32 88 28 ...... Broadcom 440x 10/100 Integrated<br>
Controller - Packet Scheduler Miniport<br>
===========================================================================<br>
===========================================================================<br>
Active Routes:<br>
Network Destination Netmask Gateway Interface Metric<br>
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.155 20<br>
10.20.0.0 255.255.0.0 10.20.30.1 10.20.30.1 30<br>
10.20.30.1 255.255.255.255 127.0.0.1 127.0.0.1 30<br>
10.255.255.255 255.255.255.255 10.20.30.1 10.20.30.1 30<br>
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1<br>
192.168.0.0 255.255.255.0 192.168.0.115 192.168.0.115 20<br>
192.168.0.115 255.255.255.255 127.0.0.1 127.0.0.1 20<br>
192.168.0.255 255.255.255.255 192.168.0.115 192.168.0.115 20<br>
224.0.0.0 240.0.0.0 10.20.30.1 10.20.30.1 30<br>
224.0.0.0 240.0.0.0 192.168.0.115 192.168.0.115 20<br>
255.255.255.255 255.255.255.255 10.20.30.1 10.20.30.1 1<br>
255.255.255.255 255.255.255.255 192.168.0.115 192.168.0.115 1<br>
Default Gateway: 192.168.0.1<br>
===========================================================================<br>
Persistent Routes:<br>
None<br>
<div><div></div><div class="h5"><br>
<br>
<br>
On Wed, Feb 3, 2010 at 9:10 AM, Anon <<a href="mailto:anon4321@gmail.com">anon4321@gmail.com</a>> wrote:<br>
>> On .168 you need to add route 10.20.0.0 mask 255.255.0.0 192.168.0.155<br>
>> This need to be done persistent (-p) or after every boot.<br>
><br>
>> Then try again ping 10.20.30.1<br>
><br>
> Did you see my latest message? It read:<br>
><br>
> "This is what I tried:<br>
><br>
> route ADD 10.20.0.0 MASK 255.255.0.0 192.168.0.155<br>
><br>
> This added the following line to the route table:<br>
><br>
> 10.20.0.0 255.255.0.0 192.168.0.155 192.168.0.188 1<br>
><br>
> But ping fails."<br>
><br>
> Is there a step I've missed?<br>
><br>
_______________________________________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br>
<a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" target="_blank">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br>
</div></div></blockquote></div><br>