I cannot even ping the LAN router on 192.168.1.1, but if I ssh though the tunnel to 192.168.1.3, I can ping it.
Investigating with tcpdump withoug guidelines is beyond my skills I'm afraid. I used tinc in router mode because it is proposed like in most howto I found... Would just switching to switch mode makes things easier or that's not related? Le sam. 12 janv. 2019 à 05:17, Hamish Moffatt <[email protected]> a écrit : > On 12/1/19 2:29 pm, Lars Kruse wrote: > > Hello > > > > > > Am Thu, 10 Jan 2019 11:58:33 +0100 > > schrieb Julien dupont <[email protected]>: > > > >> The two tunnels are working. From a client I can ping or ssh VPN_office > on > >> both tunnel and LAN IPs 172.16.0.2 and 192.168.1.3. I cannot however > ping > >> any other computer on the LAN, I get no pong back but it is not > complaining > >> he has no route to host. > > wild guess: maybe the response fails to find its way back to the source? > > In this case you could either masquerade (SNAT) traffic when it leaves > the > > tunnel at VPN_office or you could configure a suitable route on the > default > > gateway of your network (this should work for all local hosts via ICMP > > redirects). > > > In my experience the ICMP redirects don't really work. I had TINC > running on a machine other than the default gateway at one node recently > and it was a major pain - I had to configure static routes on every > machine because the ICMP redirect just didn't work. > > I since replaced the router (default gateway) with an OpenWRT setup with > TINC included and everything is much simpler. > > > Hamish > > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
