How to Install and Uninstall coturn.x86_64 Package on Fedora 34
Last updated: December 12,2024
1. Install "coturn.x86_64" package
This guide let you learn how to install coturn.x86_64 on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
coturn.x86_64
Copied
2. Uninstall "coturn.x86_64" package
This is a short guide on how to uninstall coturn.x86_64 on Fedora 34:
$
sudo dnf remove
coturn.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the coturn.x86_64 package on Fedora 34
Last metadata expiration check: 5:24:24 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : coturn
Version : 4.5.2
Release : 3.fc34
Architecture : x86_64
Size : 266 k
Source : coturn-4.5.2-3.fc34.src.rpm
Repository : fedora
Summary : TURN/STUN & ICE Server
URL : https://github.com/coturn/coturn/
License : BSD
Description : The Coturn TURN Server is a VoIP media traffic NAT traversal server and gateway.
: It can be used as a general-purpose network traffic TURN server/gateway, too.
:
: This implementation also includes some extra features. Supported RFCs:
:
: TURN specs:
: - RFC 5766 - base TURN specs
: - RFC 6062 - TCP relaying TURN extension
: - RFC 6156 - IPv6 extension for TURN
: - Experimental DTLS support as client protocol.
:
: STUN specs:
: - RFC 3489 - "classic" STUN
: - RFC 5389 - base "new" STUN specs
: - RFC 5769 - test vectors for STUN protocol testing
: - RFC 5780 - NAT behavior discovery support
:
: The implementation fully supports the following client-to-TURN-server protocols:
: - UDP (per RFC 5766)
: - TCP (per RFC 5766 and RFC 6062)
: - TLS (per RFC 5766 and RFC 6062); TLS1.0/TLS1.1/TLS1.2
: - DTLS (experimental non-standard feature)
:
: Supported relay protocols:
: - UDP (per RFC 5766)
: - TCP (per RFC 6062)
:
: Supported user databases (for user repository, with passwords or keys, if
: authentication is required):
: - SQLite
: - MySQL
: - PostgreSQL
: - Redis
:
: Redis can also be used for status and statistics storage and notification.
:
: Supported TURN authentication mechanisms:
: - long-term
: - TURN REST API (a modification of the long-term mechanism, for time-limited
: secret-based authentication, for WebRTC applications)
:
: The load balancing can be implemented with the following tools (either one or a
: combination of them):
: - network load-balancer server
: - DNS-based load balancing
: - built-in ALTERNATE-SERVER mechanism.
Available Packages
Name : coturn
Version : 4.5.2
Release : 3.fc34
Architecture : x86_64
Size : 266 k
Source : coturn-4.5.2-3.fc34.src.rpm
Repository : fedora
Summary : TURN/STUN & ICE Server
URL : https://github.com/coturn/coturn/
License : BSD
Description : The Coturn TURN Server is a VoIP media traffic NAT traversal server and gateway.
: It can be used as a general-purpose network traffic TURN server/gateway, too.
:
: This implementation also includes some extra features. Supported RFCs:
:
: TURN specs:
: - RFC 5766 - base TURN specs
: - RFC 6062 - TCP relaying TURN extension
: - RFC 6156 - IPv6 extension for TURN
: - Experimental DTLS support as client protocol.
:
: STUN specs:
: - RFC 3489 - "classic" STUN
: - RFC 5389 - base "new" STUN specs
: - RFC 5769 - test vectors for STUN protocol testing
: - RFC 5780 - NAT behavior discovery support
:
: The implementation fully supports the following client-to-TURN-server protocols:
: - UDP (per RFC 5766)
: - TCP (per RFC 5766 and RFC 6062)
: - TLS (per RFC 5766 and RFC 6062); TLS1.0/TLS1.1/TLS1.2
: - DTLS (experimental non-standard feature)
:
: Supported relay protocols:
: - UDP (per RFC 5766)
: - TCP (per RFC 6062)
:
: Supported user databases (for user repository, with passwords or keys, if
: authentication is required):
: - SQLite
: - MySQL
: - PostgreSQL
: - Redis
:
: Redis can also be used for status and statistics storage and notification.
:
: Supported TURN authentication mechanisms:
: - long-term
: - TURN REST API (a modification of the long-term mechanism, for time-limited
: secret-based authentication, for WebRTC applications)
:
: The load balancing can be implemented with the following tools (either one or a
: combination of them):
: - network load-balancer server
: - DNS-based load balancing
: - built-in ALTERNATE-SERVER mechanism.