search for: hostname_for_nod

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

...y 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 so, that makes sense). Out tinc.conf is reasonably simple: Name = $hostname_for_node Device = /dev/net/tun PingTimeout = 60 ReplayWindow = 625 ConnectTo = $remote_node_name_here ConnectTo = $remote_node2_name_here ConnectTo = $remote_node3_name_here ConnectTo = $remote_node4_name_here ConnectTo = $remote_node5_name_here ConnectTo = $remote_node6_name_here Sadly, I'm out of id...

...> > 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 so, that makes > sense). > Out tinc.conf is reasonably simple: > Name = $hostname_for_node > Device = /dev/net/tun > PingTimeout = 60 > ReplayWindow = 625 > ConnectTo = $remote_node_name_here > ConnectTo = $remote_node2_name_here > ConnectTo = $remote_node3_name_here > ConnectTo = $remote_node4_name_here > ConnectTo = $remote_node5_name_here > ConnectTo = $rem...