How to Install and Uninstall fastd.x86_64 Package on Rocky Linux 9
Last updated: November 24,2024
1. Install "fastd.x86_64" package
In this section, we are going to explain the necessary steps to install fastd.x86_64 on Rocky Linux 9
$
sudo dnf update
Copied
$
sudo dnf install
fastd.x86_64
Copied
2. Uninstall "fastd.x86_64" package
This guide covers the steps necessary to uninstall fastd.x86_64 on Rocky Linux 9:
$
sudo dnf remove
fastd.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the fastd.x86_64 package on Rocky Linux 9
Last metadata expiration check: 0:46:54 ago on Fri Feb 16 06:49:52 2024.
Available Packages
Name : fastd
Version : 22
Release : 6.el9
Architecture : x86_64
Size : 117 k
Source : fastd-22-6.el9.src.rpm
Repository : epel
Summary : Fast and secure tunneling daemon
URL : https://github.com/NeoRaider/fastd/wiki
License : BSD
Description : fastd is a secure tunneling daemon with some unique features:
:
: - Very small binary (about 100KB on OpenWRT in the default configuration,
: including all dependencies besides libc)
: - Exchangable crypto methods
: - Transport over UDP for simple usage behind NAT
: - Can run in 1:1 and 1:n scenarios
: - There are no server and client roles defined by the protocol, this is just
: defined by the usage.
: - Only one instance of the daemon is needed on each host to create a full mesh
: If no full mesh is established, a routing protocol is necessary to enable
: hosts that are not connected directly to reach each other
Available Packages
Name : fastd
Version : 22
Release : 6.el9
Architecture : x86_64
Size : 117 k
Source : fastd-22-6.el9.src.rpm
Repository : epel
Summary : Fast and secure tunneling daemon
URL : https://github.com/NeoRaider/fastd/wiki
License : BSD
Description : fastd is a secure tunneling daemon with some unique features:
:
: - Very small binary (about 100KB on OpenWRT in the default configuration,
: including all dependencies besides libc)
: - Exchangable crypto methods
: - Transport over UDP for simple usage behind NAT
: - Can run in 1:1 and 1:n scenarios
: - There are no server and client roles defined by the protocol, this is just
: defined by the usage.
: - Only one instance of the daemon is needed on each host to create a full mesh
: If no full mesh is established, a routing protocol is necessary to enable
: hosts that are not connected directly to reach each other