search for: systctl

...conf +++++ [system] path /services/puppet/common/ allow * +++++ site.pp +++++++++++++ file { "/etc/local/sysctl": owner => root, group => root, mode => 750, source => "puppet://puppet/system/$name" } and get "/etc/local/systctl" from "/services/puppet/common/etc/local/sysctl" on the server. But instead of it, strangely enough an empty /etc/local/systctl directory were created on the client machine. Is it a feature or a misconfiguration on my part? Best regards, Jozsef -- E-mail : kadlec@sunserv.kfki.hu...

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 my reply, but.. maybe I can get you to confirm what you mean by INSIDE node? > Do you mean the node on the LAN that runs tinc,...

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/systctl.conf and can confirm now after a reboot that it's enabled. Unfortunately, still can't ping the node on the LAN. OK , let's just do one other simple thing before we continue, could you post the output of iptables -vnL FORWARD as long as it doesn't reveal anything you would prefer no...

I am running Debian Squeeze with Xen 4.0. I am running a stress test. I have created 2 virtual machines, each with 512 Mb of memory adn 8Gb in size. I have made one of the vms an NFS server, sharing out a large file (4.6 Gb). The other virtual machine is an NFS client. The stress test consists of passing that big file back and forth via an mv command executed on the client, which moves the file

...uck.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/systctl.conf and can confirm now after a reboot that it's enabled. Unfortunately, still can't ping the node on the LAN. OK , let's just do one other simple thing before we continue, could you post the output of iptables -vnL FORWARD as long as it doesn't reveal anything you would prefer no...

I have a 4 Node Tinc VPN setup with 2 nodes on my LAN and the other 2 outside the LAN in the cloud. Everything has been working great for about 5 years now, until today when I decided to move one of the nodes to another box. I basically, copied over the /etc/tinc folder to the new server and also moved the /etc/network/interfaces file, so that the new server was an exact mirror (more or less).