Displaying 3 results from an estimated 3 matches for "remote_node4_name_here".
Did you mean:
remote_node2_name_here
2017 May 17
2
Improving packets/sec and data rate - v1.0.24
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
2017 May 17
0
Improving packets/sec and data rate - v1.0.24
.../ 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 ideas on how to improve the performance here. I've
tried to change the following sysctl settings:
net.core.somaxconn='4096'
net.core.rmem_max='16777216'
net.core.wmem_max='16777216...
2017 May 17
2
Improving packets/sec and data rate - v1.0.24
...s
> 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 ideas on how to improve the performance here. I've
> tried to change the following sysctl settings:
> net.core.somaxconn='4096'
> net.core.rmem_max='16777216...