server: disable tcpkeepalive #2635
Conversation
The default value for tcpkeepalive in the standard net package is 15 seconds, while the default value for BGP keepalive is 30 seconds. If the network is not good, the TCP connection is disconnected before BGP can send keepalive messages. Therefore, BGP keepalive is effectively invalid. The solution is that since we have BGP keepalive, we don't need to open tcp keepalive. Signed-off-by: Chen Yahui <goodluckwillcomesoon@gmail.com>
|
looks like frr supports tcp keepliave. bird doesn't use. Not sure what is appropriate. I tend to keep this alone because nobody hasn't complained about this until now. |
Unfortunately, we've had this problem for over a year. The network of our cloud IAAS is complex. When there is heavy traffic, the BGP connection may be disconnected. We tried to adjust the Finally, we locate the root cause of the problem is the |
|
By default, the socket created by syscall does not enable tcpkeepalive. However, golang's net package enables the socket tcpkeepalive and sets the keepalive period to 15 seconds by Therefore, modifying the tcpkeepalive configuration of the OS does not affect this bug.
|
The default value for tcpkeepalive in the golang net package is 15 seconds, while the default value for BGP keepalive is 30 seconds. If the network is not good, the TCP connection is disconnected before BGP can send keepalive messages.
Therefore, BGP keepalive is effectively invalid.
The solution is that since we have BGP keepalive, we don't need to open tcp keepalive.