finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Make it obvious that running Coturn in host-networking mode requires manual firewall changes

Browse Source
This commit is contained in:
Slavi Pantaleev 2023-01-26 17:59:56 +02:00
parent 867737fe0b
commit f1c9052fe5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -10,8 +10,8 @@ Such deployments don't need to run Coturn within a private container network any
matrix_coturn_docker_network: host matrix_coturn_docker_network: host
``` ```
With such a configuration, Docker no longer needs to configure thousands of firewall forwarding rules each time Coturn starts and stops. With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops.
You may, however, need to allow these ports in your firewall configuration yourself. This, however, means that **you will need to ensure these ports are open** in your firewall yourself.
Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network. Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network.