https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-08-01T11:04:30ZOpen Source Mobile Communicationslibosmocore - Bug #3441: two processes can open the same UDP port without errorhttps://osmocom.org/issues/3441?journal_id=105572018-08-01T11:04:30Zdexter
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>The problem should be fixed now. I also noticed a missing return code check. See also:</p>
<p><a class="external" href="https://gerrit.osmocom.org/#/c/libosmocore/+/10288">https://gerrit.osmocom.org/#/c/libosmocore/+/10288</a> socket: check return code of setsockopt<br /><a class="external" href="https://gerrit.osmocom.org/#/c/libosmocore/+/10289">https://gerrit.osmocom.org/#/c/libosmocore/+/10289</a> socket: do not set SO_REUSEADDR for IPPROTO_UDP</p> libosmocore - Bug #3441: two processes can open the same UDP port without errorhttps://osmocom.org/issues/3441?journal_id=105662018-08-02T10:28:25Zdexter
<ul></ul><p>I have now tested everything and I do not see any problems with fallout. Except osmo-mgw had problems with its unit-tests because one of the test function did not close the connections it created for the test, resulting in different ports on the following test. This also means that the applications internally did not notice that they re-use ports. This is now fixed.</p>
<p>See also:<br /><a class="external" href="https://gerrit.osmocom.org/#/c/osmo-mgw/+/10306/">https://gerrit.osmocom.org/#/c/osmo-mgw/+/10306/</a></p>
<p>and</p>
<p><a class="external" href="https://gerrit.osmocom.org/#/c/libosmocore/+/10289/">https://gerrit.osmocom.org/#/c/libosmocore/+/10289/</a></p> libosmocore - Bug #3441: two processes can open the same UDP port without errorhttps://osmocom.org/issues/3441?journal_id=106062018-08-06T13:09:45Zdexter
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul>