Skip to content

coturn: Use wildcard listening address to fix startup issues

Sunil Mohan Adapa requested to merge sunilmohan/freedombox:coturn-start-fix into master

Fixes: #2069 (closed).

Without a listening port, coturn will try to enumerate the non-local IP addresses and try to listen on them. If coturn is started before network is fully setup, it finds no usable IP addresses and fails. Furthermore, if IPs are added to the system, it does not automatically listen on them.

A better approach as advised by systemd NetworkTarget documentation is to listen on a wildcard address. This does not require network to be online and works well for IP addresses being added/removed from the system. coturn is itself unable to make changes to its default listening behavior for backward compatibility.

Tests:

  • Freshly install coturn. Observe that listening-ip is properly set in the configuration file. coturn is listening on 3478, 3479, 5349, 5350. coturn is listening on ::1 and * addresses instead of individual IP addresses.

  • Install coturn without the patch. Apply the patch and restart FreedomBox. coturn setup will run. listening-ips get added to the configuration file. The static-auth-secret is not changed from earlier. coturn will be restarted. coturn is listening on 3478, 3479, 5349, 5350. coturn is listening on ::1 and * addresses instead of individual IP addresses.

  • Install coturn without the patch. Disable coturn. Apply the patch and restart FreedomBox. coturn setup will run. coturn will not be enabled. coturn will be running after setup.

  • Functional tests pass.

  • All ports able to connect using netcat (nc command) with IPv4 (-4 option) and IPv6 (-6 option).

Signed-off-by: Sunil Mohan Adapa sunil@medhas.org

Merge request reports