View Source eturnal STUN/TURN Server
eturnal is a modern, straightforward STUN and TURN server with full IPv6 support. For TURN authentication, the mechanism described in the REST API for Access to TURN Services specification is implemented.
On APT-based Linux distributions, run:
sudo apt install extrepo sudo extrepo enable eturnal sudo apt update sudo apt install eturnal
On DNF-based Linux distributions, run:
sudo dnf config-manager --add-repo https://eturnal.net/eturnal.repo sudo dnf install eturnal sudo systemctl --now enable eturnal
On YUM-based Linux distributions, run:
sudo yum-config-manager --add-repo https://eturnal.net/eturnal.repo sudo yum install eturnal sudo systemctl --now enable eturnal
On SUSE Linux Enterprise and openSUSE systems, distribution repositories can be used instead. On other Linux systems, the binary release can be installed as described in the reference documentation. For Windows, an installer is available. On other platforms, eturnal is built from source.
The eturnal server is configured by editing the
/etc/eturnal.yml file. This
file uses the (indentation-sensitive!) YAML format. For TURN relaying to
work, you'll have to specify the shared authentication
secret and (at
least if the server is running behind NAT) also the
which should be set to the server's external IPv4 address. As an example, a
minimal configuration for offering STUN and TURN services on port 3478 (UDP and
TCP) might look like this:
eturnal: secret: "long-and-cryptic" # Shared secret, CHANGE THIS. relay_ipv4_addr: "203.0.113.4" # The server's public IPv4 address. relay_ipv6_addr: "2001:db8::4" # The server's public IPv6 address (optional).
A more detailed, commented example configuration is shipped with the eturnal server.
For controlling eturnal, the
eturnalctl command can be used; see:
If eturnal was started by systemd, log files are written into the
/var/log/eturnal directory by default. In order to log to the journal
log_dir option can be set to
stdout in the configuration file.
Please use our issue tracker for bug reports and feature requests. Feel
free to (ab)use it for usage questions as well. If you happen to be using
XMPP, you could also join our public channel