<div dir="ltr">Hi Lars,<div><br></div><div>Thanks for the help</div><div><br></div><div>** Test 1 ** </div><div>On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3'</div><div>When pinging 192.168.1.1 from client 1, with no success, I see no packet passing.</div><div><div>When pinging 192.168.1.3 from client 1, with success, I see packet passing:</div>IP 172.16.0.3 > <a href="http://192.168.1.3">192.168.1.3</a>: ICMP echo request, id 2648, seq 23, length 64</div><div>IP 192.168.1.3 > <a href="http://172.16.0.3">172.16.0.3</a>: ICMP echo request, id 2648, seq 23, length 64</div><div>...</div><div><br></div><div>** Test 2 *</div><div>I use a machine from the office LAN with IP 192.168.1.100 to ping VPN_office (172.16.0.2), VPN_out (172.16.0.1) and VPN_client (172.16.0.3) - I can't access the router right now. They all work. Here is the output of VPN_client:</div><div>> ping 172.16.0.3</div><div>PING 172.16.0.3 (172.16.0.3) 56(84) bytes of data.</div><div><div>From 192.168.1.1 icmp_seq=2 Redirect Host (New nexthop: 192.168.1.3)</div><div>From <a href="http://192.168.1.1">192.168.1.1</a>: icmp_seq=2 Redirect Host (New nexthop: 192.168.1.3)</div><div>...</div><div><br></div><div>This is the result of the traffic redirection rule I put in the router.</div><br class="gmail-Apple-interchange-newline"></div></div><br><div class="gmail_quote"><div dir="ltr">Le lun. 14 janv. 2019 à 19:43, Lars Kruse <<a href="mailto:lists@sumpfralle.de">lists@sumpfralle.de</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Julien,<br>
<br>
<br>
Am Mon, 14 Jan 2019 18:04:40 +0100<br>
schrieb Julien dupont <<a href="mailto:marcelvierzon@gmail.com" target="_blank">marcelvierzon@gmail.com</a>>:<br>
<br>
> Investigating with tcpdump withoug guidelines is beyond my skills I'm<br>
> afraid.<br>
<br>
Try this on your VPN_office host:<br>
tcpdump -npi any icmp and host 192.168.1.3<br>
In parallel you start a ping from the other network:<br>
ping 192.168.1.1<br>
<br>
I assume, that tcpdump will show all packets from your source. Probably you<br>
will see two packets each (with a slight delay of a few milliseconds). These<br>
are the packets forwarded to the outgoing interface.<br>
Furthermore I assume, that you do not see any return traffic.<br>
<br>
Feel free to share a few lines of seemingly relevant output from tcpdump with<br>
us.<br>
<br>
Another (unrelated) test:<br>
Please run "ping SOME_IP_FROM_THE_OTHER_NETWORK" on 192.168.1.1.<br>
Please share the output with us.<br>
I assume, that the packet goes out via your WAN (instead of flowing towards<br>
192.168.1.3) and is thus rightfully rejected.<br>
<br>
<br>
> I used tinc in router mode because it is proposed like in most howto I<br>
> found... Would just switching to switch mode makes things easier or that's<br>
> not related?<br>
<br>
No, router mode should be fine for your purpose.<br>
<br>
Cheers,<br>
Lars<br>
_______________________________________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">tinc@tinc-vpn.org</a><br>
<a href="https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" rel="noreferrer" target="_blank">https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br>
</blockquote></div>