Cellular Network Infrastructure » Radio Access Network » OsmoBTS

socket.c has now an additional flag (OSMO_SOCK_F_UDP_REUSEADDR) that the user can pass in order to restore the old behavior. Since we do not have much applications that use multicast I think this is a good compromise. Unfortunately it was not possible to set SO_REUSEADDR after calling the osmo_sock... API. This is because the the function would exit with an error. SO_REUSEADDR must be set before the bind(). Also using a flag looks cleaner to me than to modify the socket parameters by hand after the api-call.

See also:
https://gerrit.osmocom.org/#/c/libosmocore/+/10587 socket: add flag to enforce SO_REUSEADDR on UDP sockets
https://gerrit.osmocom.org/#/c/libosmocore/+/10588 gsmtap_util: make sure SO_REUSEADDR is applied for GSMTAP
https://gerrit.osmocom.org/#/c/osmo-bts/+/10589 osmo_mcast_sock: make sure SO_REUSEADDR is applied
https://gerrit.osmocom.org/#/c/osmocom-bb/+/10590 osmo_mcast_sock: make sure SO_REUSEADDR is applied

All the patches are through. Also I did not observe any new problems. The communication between osmo-bts-virtual and virtphy looks fine.