diff options
| author | Harald Welte <laforge@osmocom.org> | 2020-03-08 21:50:01 +0100 |
|---|---|---|
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2020-03-09 12:00:24 +0100 |
| commit | fb3a57f7a486d449951f9f9a5e18e98b3ece7b2b (patch) | |
| tree | d2a5bcb0e1de3ac6dd2318f8174d4992d0255b87 /src/trau | |
| parent | 8d31d71882292522457811a84e73dacb625815ea (diff) | |
ortp: disable SO_REUSEADDR + SO_REUSEPORT
ortp >= 0.24.0 doesn't differentiate between SO_REUSEADDR and
SO_REUSEPORT, and has both enabled by default. The latter means that
we can end up with non-unique port bindings as we will not fail to
bind the same port twice.
This should have caused visible problems not only when operating multiple
osmo-bts on one machine (rare), but also with a single osmo-bts. Once the range
(default 16384-17407 ) wraps, there is a risk of new sockets (for new cals)
colliding with old ones. As two ports (RTP+RTCP) are used per call, this means
every 512 voice calls we expect the BTS to wrap. And from that point onwards
there's a risk of overlapping with previously allocated sockets.
Change-Id: I4fc9eee561c7958c70c63b4ffdc6cb700b795e28
Closes: OS#4444
Diffstat (limited to 'src/trau')
| -rw-r--r-- | src/trau/osmo_ortp.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/src/trau/osmo_ortp.c b/src/trau/osmo_ortp.c index 1d652cb..0fd30df 100644 --- a/src/trau/osmo_ortp.c +++ b/src/trau/osmo_ortp.c @@ -378,6 +378,12 @@ struct osmo_rtp_socket *osmo_rtp_socket_create(void *talloc_ctx, unsigned int fl rtp_session_set_profile(rs->sess, osmo_pt_profile); rtp_session_set_jitter_compensation(rs->sess, 100); + /* ortp >= 0.24.0 doesn't differentiate between SO_REUSEADDR and + * SO_REUSEPORT, and has both enabled by default. The latter means that + * we can end up with non-unique port bindings as we will not fail to + * bind the same port twice */ + rtp_session_set_reuseaddr(rs->sess, false); + rtp_session_signal_connect(rs->sess, "ssrc_changed", (RtpCallback) ortp_sig_cb_ssrc, RTP_SIGNAL_PTR_CAST(rs)); |