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
Hi team,
I am using libwebsockets-v4.3.2 as wss client to connect servers now.
There was an issue when client attempted to bind the specific ip and port within the range allowed by the Linux firewall before connecting.
I notice that there is a iface parameter in the lws_client_connect_info struct to bind a specific interface or IP in source code.
But I observe that the port is set to 0 when lws_socket_bind is called in the function lws_client_connect_3_connect, which means the client will pick an ephemeral port.
I was surprised to find out that the feature (source port setting) has already been implemented on the main branch since 2022. so I would like to inquire if there are any plans to release this feature later?
The text was updated successfully, but these errors were encountered:
Hi team,
I am using
libwebsockets-v4.3.2
as wss client to connect servers now.There was an issue when client attempted to bind the specific ip and port within the range allowed by the Linux firewall before connecting.
I notice that there is a
iface
parameter in thelws_client_connect_info
struct to bind a specific interface or IP in source code.But I observe that the port is set to 0 when
lws_socket_bind
is called in the functionlws_client_connect_3_connect
, which means the client will pick an ephemeral port.I was surprised to find out that the feature (source port setting) has already been implemented on the main branch since 2022.
so I would like to inquire if there are any plans to release this feature later?
The text was updated successfully, but these errors were encountered: