Actions
Bug #4444
closedports not unique when running multiple osmo-bts on the same machine
Start date:
03/08/2020
Due date:
% Done:
100%
Spec Reference:
Description
This is with running two osmo-bts[-virtual] on the same machine and a number of active voice calls:
root@36bd59f48d7c:/docker# ./netstat -uan Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State udp 768 0 172.18.23.4:16384 0.0.0.0:* udp 0 0 172.18.23.4:16384 0.0.0.0:* udp 0 0 172.18.23.4:16385 0.0.0.0:* udp 0 0 172.18.23.4:16385 0.0.0.0:* udp 768 0 172.18.23.4:16386 0.0.0.0:* udp 0 0 172.18.23.4:16386 0.0.0.0:* udp 0 0 172.18.23.4:16387 0.0.0.0:* udp 0 0 172.18.23.4:16387 0.0.0.0:* udp 0 0 172.18.23.4:16388 0.0.0.0:* udp 0 0 172.18.23.4:16388 0.0.0.0:* udp 0 0 172.18.23.4:16389 0.0.0.0:* udp 0 0 172.18.23.4:16389 0.0.0.0:* udp 0 0 172.18.23.4:16390 0.0.0.0:* udp 0 0 172.18.23.4:16391 0.0.0.0:* udp 0 0 172.18.23.4:16392 0.0.0.0:* udp 0 0 172.18.23.4:16393 0.0.0.0:* udp 0 0 172.18.23.4:16394 0.0.0.0:* udp 0 0 172.18.23.4:16395 0.0.0.0:* udp 0 0 172.18.23.4:16396 0.0.0.0:* udp 0 0 172.18.23.4:16397 0.0.0.0:*
16384 is bts->rtp_port_range_start. So both of them happily start to bind ports from 16384 upwards without creating any error whatsoever. This means that the bind_rtp()
loop in source:src/common/rsl.c is not working at all.
Related issues
Actions