Thanks again Keith. I disabled UFW and flushed iptables completely, but same result. Pings from the external node are reaching the internal node on the tinc0 interface but nothing happens after that. Now that I'm thinking of it, I did some masquerading in order to get OpenVPN to work on another box, I wonder if that would be applicable here?
Very Respectfully, Kismet Agbasi -----Original Message----- From: Keith [mailto:[email protected]] Sent: Thursday, October 6, 2016 10:47 AM To: [email protected]; [email protected] Subject: Re: Can't Route LAN Traffic Behind Tinc Network On 06/10/2016 16:33, Kismet Agbasi wrote: > Thanks Keith. Here's the output: OK. I'd like to say that I recognize this is now off topic for the tinc list, as it really is about basic routing and firewalls and has little if anything to do with tinc at this point. However, it's a low volume list, so unless anyone complains, lets thrash it out here. > wrong interface......hmmm. As you can tell I use UFW so here's the output of > "ufw status numbered": > > root@ubuntu2:~# ufw status numbered > Status: active I'm actually unfamiliar with ufw, as I am with most of the plethora of iptables-helpers out there. I could ask you to post a list of all tools and chain, (iptables -vnL) but can we just do something simple first as a test? Can you disable your ufw and then run iptables -F FORWARD (just to be sure) and then test your tinc<->LAN connectivity? your default FORWARD POLICY is ACCEPT so this quick check should let us know if the firewall rules are getting in the way. I guess you should quicky re-enable your ufw rules then, so as not to remain unprotected. You have a public IP on this box, I understand. K/ _______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
