diff options
author | Harald Welte <laforge@osmocom.org> | 2020-03-08 21:50:01 +0100 |
---|---|---|
committer | Harald Welte <laforge@osmocom.org> | 2020-03-09 11:24:45 +0100 |
commit | 54c919ec480bd1063b9dd9b5d23661ccaaa9b85e (patch) | |
tree | 9e1c83228ed24ad98b1a4a6eb9f0d495a2c50063 /debian/changelog | |
parent | 9104597d7656c1914d71951c4894c89172ade624 (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 'debian/changelog')
0 files changed, 0 insertions, 0 deletions