Lars, Thanks for that tcpdump command, very helpful. I was able to confirm that the packets are indeed reaching the INSIDE node - so I'm suspecting that my routing table might be wrong.
Very Respectfully, Kismet Agbasi -----Original Message----- From: tinc [mailto:[email protected]] On Behalf Of Lars Kruse Sent: Wednesday, October 5, 2016 4:18 PM To: [email protected] Subject: Re: Can't Route LAN Traffic Behind Tinc Network Hi Kismet, Am Wed, 5 Oct 2016 10:13:13 -0400 schrieb "Kismet Agbasi" <[email protected]>: > At this point I'm unsure of which information to provide in order to > elicit some assistance, however, below is the routing table of one > INTERNAL and EXTERNAL node. I basically want to be able to reach the > 172.23.6.0 network from any of the EXTERNAL nodes - any assistance would be > highly appreciated. I suggest to send pings from the source to the target and try to verify the packets along their way. "tcpdump" is usually a good tool for this: tcpdump -ni any icmp (replace "any" with a specific interface in order to make sure that the traffic is on the right track) Afterwards you will have a better feeling whether you need to check the forward or the return traffic and at which specific node the routing or the firewall rules are not acting in line with your plan. Cheers, Lars _______________________________________________ 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
