-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey @lance5890 - Thanks for your question. If I understand correctly, what you're seeing is the connection from an etcd client, through to an etcd member and you're curious how the etcd client decided on port Assuming I have the question right, in etcd, the client-to-server communication port range is determined by the operating system and network configuration. By default, etcd clients use a dynamically allocated port for communication with the etcd members. This dynamic port range is assigned by the operating system's networking stack. The client-to-server communication ports are typically chosen from the range of available ephemeral ports on the system. Ephemeral ports are used for outbound connections from the client, and the exact range can vary based on the operating system. If you want to restrict the range of dynamic ports that etcd clients use for connecting to etcd members, you would need to adjust the network settings of the operating system itself. However, please note that this is not a typical configuration and might have broader implications for other applications and services running on the system. Refer to the linux kernel docs for |
Beta Was this translation helpful? Give feedback.
Hey @lance5890 - Thanks for your question.
If I understand correctly, what you're seeing is the connection from an etcd client, through to an etcd member and you're curious how the etcd client decided on port
50936
when making the call across to the member/etcd server on port2379
?Assuming I have the question right, in etcd, the client-to-server communication port range is determined by the operating system and network configuration. By default, etcd clients use a dynamically allocated port for communication with the etcd members. This dynamic port range is assigned by the operating system's networking stack.
The client-to-server communication ports are typically chosen from the range of…