search for: pallinger

On Mon, 4 May 2020 18:45:19 +0200 (CEST) Sven-Haegar Koch <haegar at sdinet.de> wrote: > On Mon, 4 May 2020, Pallinger Péter wrote: > > > ------- TL;DR ------- > > > > Performance seems slow (around 300-400Mbit peak). > > How to improve? > > Not sure if that could be the case for you, my links are not that > fast: > > Make sure to disable compression, that is a known...

On Tue, 5 May 2020 10:56:01 +0200 Pallinger Péter <pallinger at dsd.sztaki.hu> wrote: > On Mon, 4 May 2020 18:45:19 +0200 (CEST) > Sven-Haegar Koch <haegar at sdinet.de> wrote: > > On Mon, 4 May 2020, Pallinger Péter wrote: > > > > Make sure to disable compression, that is a known CPU hog. > > C...

On Tue, 5 May 2020 13:32:50 +0100 Jonathan Plews <SRS0=286U=6T=yahoo.co.uk=pl3w5y at mijnuvt.nl> wrote: > I didn't study the internals but maybe changing DirectOnly, Forwarding > and IndirectData will have an impact on per packet performance and > speed stability by disabling some of the meshing features? I will definitely try those. > Although it probably just hit the CPU

------- TL;DR ------- Performance seems slow (around 300-400Mbit peak). How to improve? ------- The Long Version ------- I tried to test tinc performance for an upcoming project that may need to use NFS over a VPN. Our current tinc network seems to be able to transmit at around 30-40 MB/s. (I used an 1GB random testfile to copy to/from /dev/shm/; using netcat and http.) In comparison, HTTP and

On Mon, 4 May 2020, Pallinger Péter wrote: > ------- TL;DR ------- > > Performance seems slow (around 300-400Mbit peak). > How to improve? Not sure if that could be the case for you, my links are not that fast: Make sure to disable compression, that is a known CPU hog. Greetings, Haegar -- Three may keep a se...

On Thu, 7 May 2020, Pallinger Péter wrote: > Also, my question about the stability of tinc 1.1 still stands. Is it > ready for production? I am personally only using tinc 1.1 pre17+git, but in our network are also still some older nodes. No problems seen currently. c'ya sven-haegar -- Three may keep a secret, i...

...that is triggered by strange coincidences that need many hosts in the network. Any tips to solve this mystery are appreciated! Thanks in advance: PP ----- P.s.: additional information (maybe relevant?): The big tinc network is installed using the modified ansible-tinc role: https://github.com/pallinger/ansible-tinc, forked from thisismitch/ansible-tinc. The main difference is that I can limit ConnectTo hosts (all hosts were added as ConnectTo in the original ansible role), as too many ConnectTo hosts caused some tinc versions (the old ones, maybe (I forgot)) to spin the CPU for more than 10 minut...