You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We struggled yesterday about max connection burst problems. It take some time to find out the reason/find a workaround, since there is no logging message, when a connection burst occurs. Would it be possible to print a logging message in this situation? One per second should be fine.
The text was updated successfully, but these errors were encountered:
The commit 46f3eba changes the default value of max_connection_burst from 100 to 10. The hosted documentation lists the 100 as default value. https://www.tinc-vpn.org/documentation-1.1/tinc.conf.5.html
Was this change indented?
We struggled yesterday about max connection burst problems. It take some time to find out the reason/find a workaround, since there is no logging message, when a connection burst occurs. Would it be possible to print a logging message in this situation? One per second should be fine.
The text was updated successfully, but these errors were encountered: