search for: centraltruck

...-- From: tinc [mailto:tinc-bounces at tinc-vpn.org] On Behalf Of Lars Kruse Sent: Wednesday, October 5, 2016 4:18 PM To: tinc at tinc-vpn.org Subject: Re: Can't Route LAN Traffic Behind Tinc Network Hi Kismet, Am Wed, 5 Oct 2016 10:13:13 -0400 schrieb "Kismet Agbasi" <kagbasi at centraltruck.net>: > 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...

...ing UFW fixed it for me: " -A POSTROUTING -s 10.9.0.0/24 -o eth1 -j MASQUERADE" Very Respectfully, Kismet-Gerald Agbasi IT/Systems Administrator Central Truck Center, Inc. Office: 240-487-3315 Toll Free: 1-800-492-0709 Fax: 240-487-3399 3839 Ironwood Place Landover, MD 20785 www.centraltruckcenter.com This message may contain confidential and/or proprietary information, and is intended for the person or entity to which it is addressed. Any use by others for all other purposes is strictly prohibited. ___________________________________________________________________________________...

...4] 655 ALLOW IN Anywhere [ 5] DNS ALLOW IN Anywhere Very Respectfully, Kismet Agbasi -----Original Message----- From: Keith [mailto:keith at rhizomatica.org] Sent: Thursday, October 6, 2016 10:14 AM To: tinc at tinc-vpn.org; kagbasi at centraltruck.net Subject: Re: Can't Route LAN Traffic Behind Tinc Network On 06/10/2016 15:48, Kismet Agbasi wrote: >> Did you remember to activate kernel ip forwarding? >> i.e. echo 1 > /proc/sys/net/ipv4/ip_forward ? > I actually forgot to do this, but I have enabled it now in /etc/sys...

...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:keith at rhizomatica.org] Sent: Thursday, October 6, 2016 10:47 AM To: kagbasi at centraltruck.net; tinc at tinc-vpn.org 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 fi...

Hi Kismet, Am Wed, 5 Oct 2016 10:13:13 -0400 schrieb "Kismet Agbasi" <kagbasi at centraltruck.net>: > 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 ass...

...0 172.23.6.1 255.255.255.0 UG 0 0 0 eth1 Very Respectfully, Kismet-Gerald Agbasi IT/Systems Administrator Central Truck Center, Inc. Office: 240-487-3315 Toll Free: 1-800-492-0709 Fax: 240-487-3399 3839 Ironwood Place Landover, MD 20785 www.centraltruckcenter.com This message may contain confidential and/or proprietary information, and is intended for the person or entity to which it is addressed. Any use by others for all other purposes is strictly prohibited. ____________________________________________________________________________ ___...

Keith, Thanks for the reply and the pointers. > Did you remember to activate kernel ip forwarding? > i.e. echo 1 > /proc/sys/net/ipv4/ip_forward ? I actually forgot to do this, but I have enabled it now in /etc/systctl.conf and can confirm now after a reboot that it's enabled. Unfortunately, still can't ping the node on the LAN. > and when I saw that I was about to cancel

I am currently out of the office; returning on Tuesday 3/29/2016, at which time I will respond to all emails. If this is an urgent matter, please call my colleague Sharon Roberts at 301322900 x140.

Thank you guys for a great product. I have successfully setup a VPN between a cloud server and an internal one (details below). However, I am unable to pass traffic from the cloud to the internal machines behind the tunnel. Internal subnet: 172.23.6.0/24 Host Public IP: 50.242.184.132 Host LAN IP: 172.23.6.148 Host VPN IP: 10.9.0.2 Cloud Server IP: 107.170.55.181 Cloud Server