search for: dachari

Hi, In a setup where OpenVSwitch is used with GRE tunels on top of an interface provided by tinc, I'm experiencing significant performance degradation problems (from 100Mb/s down to 1Mb/s in the worst case) and I'm not sure how to fix this. The manifestation of the problem is, from the user point of view, iperf reports ~100Mb/s and rsync reports ~1Mb/s: $ iperf -c 91.224.149.132

Signed-off-by: Loic Dachary <loic at dachary.org> --- doc/tinc.conf.5.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tinc.conf.5.in b/doc/tinc.conf.5.in index 7196392..00e4674 100644 --- a/doc/tinc.conf.5.in +++ b/doc/tinc.conf.5.in @@ -416,7 +416,7 @@ and are available. .El .It Va ReplayWindow Li = Ar bytes Pq 16 -vhis is the size of the replay tracking

Hi, I wrote a draft puppet module to maintain a L2 mesh based on tinc [1]. I tried to explain what it is about so that it makes sense even to people who know nothing about tinc [2]. Before polishing it so that it can be useful to the general public instead of just myself, I would very much appreciate your comments. This is my first experience with tinc and I would like to improve :-) Thanks for

[Disclaimer : I'm not a network engineer] Hi, In a setup where OpenVSwitch is used with GRE tunels on top of an interface provided by tinc, I'm experiencing MTU problems and I'm not sure how to fix them. The manifestation of the problem is, from the user point of view, communication hang. And using "tcpdump -i there" displays lines such as : 18:54:00.345666 IP

When installing stackdriver on an ubuntu 12.04 machine, I get the following error: change from notrun to 0 failed: /usr/bin/apt-key: 8: /usr/bin/apt-key: mktemp: not found Based on the instructions here <http://feedback.stackdriver.com/knowledgebase/articles/206135-ubuntu> on their website, my resource is as follows: exec { ''add-stackdriver-key'': command =>

With pleasure we announce the release of tinc version 1.0.24. Here is a summary of the changes: * Various compiler hardening flags are enabled by default. * Updated support for Solaris, allowing switch mode on Solaris 11. * Configuration will now also be read from a conf.d directory. * Various updates to the documentation. * Tinc now forces glibc to reload /etc/resolv.conf after it

With pleasure we announce the release of tinc version 1.0.24. Here is a summary of the changes: * Various compiler hardening flags are enabled by default. * Updated support for Solaris, allowing switch mode on Solaris 11. * Configuration will now also be read from a conf.d directory. * Various updates to the documentation. * Tinc now forces glibc to reload /etc/resolv.conf after it

Hi, I setup tinc on two hosts with IP 192.168.200.102 on the first and IP 192.168.200.101 on the second. And it works. Now I would like to route packets thru 192.168.200.101 from 192.168.200.102 by adding the following route: ip route add 10.10.70.0/24 via 192.168.200.101 dev TINCDEVICE However, when I ping 10.10.70.254 from 192.168.200.102, I see the packet being sent to TINCDEVICE (tcmpdump)

Hi, Is there a way to test for exported resources using rspec-puppet ? I found a post explaining how it could be done with cucumber ( http://blog.nistu.de/2011/09/04/testing-exported-resources-with-cucumber-puppet ) but could not find examples or documentation for rspec-puppet. Cheers -- You received this message because you are subscribed to the Google Groups "Puppet Users"