Hey,
osmo_sock_init is nice but I have hit a missing feature. I want to be able to make an outgoing connection but need to specify the src ip (and maybe src port too).
a.) I could extend osmo_sock_init to have a src_ip and src_port in the parameter and issue a bind between the socket(2) and connect(2).
b.) I could add a cb function that is passing the fd to the cb and do the bind (or others do setsockopt).
Any other ideas? Preferences? Comments?
holger
Hi.
Currently there's a way to init and register socket for "server side" (BSC_FD_READ) via osmo_sock_init_ofd() but there seems to be no counterpart for "client side" (BSC_FD_WRITE) which could be useful in few places too.
We can modify osmo_sock_init_ofd() to check for OSMO_SOCK_F_CONNECT flag and register with BSC_FD_WRITE or we can add separate function. Or maybe it's already available somehow and I just don't see it.
On 17.01.2017 15:34, Holger Freyther wrote:
Hey,
osmo_sock_init is nice but I have hit a missing feature. I want to be able to make an outgoing connection but need to specify the src ip (and maybe src port too).
a.) I could extend osmo_sock_init to have a src_ip and src_port in the parameter and issue a bind between the socket(2) and connect(2).
b.) I could add a cb function that is passing the fd to the cb and do the bind (or others do setsockopt).
Any other ideas? Preferences? Comments?
holger
See also gerrit #1624 for proposed implementation.