search for: techsmix

Hi, We've been running tinc for a while now but, have started hitting a bottleneck where the number of packets/sec able to be processed by our Tinc nodes is maxing out around 4,000 packets/sec. Right now, we are using the default cipher and digest settings (so, blowfish and sha1). I've been testing using aes-256-cbc for the cipher and seeing ~5% increases across the board. Each Tinc node

...ng that happens when sending a packet. I've done some testing with wireguard and that has a lot better performance but it's still changing quite a lot and only does a subset of what tinc does so probably not a stable solution. Martin On Wed, 17 May 2017 at 18:05 Jared Ledvina <jared at techsmix.net> wrote: > Hi, > > Terribly sorry about the duplicated message. > > I've completed the upgrade to Tinc 1.0.31 but, have not seen much of a > performance increase. The change looks to be similar to switching to > both aes-256-cbc w/ sha256 (which are now the default s...

...eraging around 26% over the bandwidth being availible over the tinc network versus over the internet. Is that % overhead expected or have we just poorly configured something? Totally willing to grab any numbers/stats that might assist here. Thanks again, Jared -- Jared Ledvina jared at techsmix.net On Tue, May 16, 2017, at 05:08 PM, Jared Ledvina wrote: > Hi, > > We've been running tinc for a while now but, have started hitting a > bottleneck where the number of packets/sec able to be processed by our > Tinc nodes is maxing out around 4,000 packets/sec. > > Rig...

Niklas - Thanks! Yeah, your Github issue was very useful for me to understand what is probably causing our issue (the syscall chain done on every UDP packet). Very interesting that you're able to see around 90% of a Gig line on bare metal. Were you ever able to make any further progress on adjusting Tinc based on the investigation in https://github.com/gsliepen/tinc/issues/110 ? Martin -