How to Install Zeek (Formerly Bro IDS) on Fedora 44
Bro IDS is now called Zeek. Install the current LTS release on Fedora 44 from the project's own repository, point it at an interface and read the logs.
Bro IDS still exists, but under a different name: the project announced in October 2018 that it would become Zeek, and since Zeek 3.0 the programs are called zeek and zeekctl instead of bro and broctl. Fedora 25 is long past its end of life, and the bro package that older tutorials install with dnf install bro is no longer what the project ships. This guide installs the current long-term-support release of Zeek on Fedora 44 from the project's own package repository, configures a single standalone sensor with ZeekControl, and shows where the logs end up.
Zeek is a passive network traffic analyzer. It watches an interface, writes detailed logs about every connection, DNS query, HTTP request, TLS handshake and more, and can raise notices about suspicious activity. It does not block traffic.
Requirements
- A server running Fedora 44 (x86_64 or aarch64) with a user that can run
sudo. The Zeek project publishes packages for Fedora 43, Fedora 44 and Rawhide; the steps are the same on Fedora 43 with the release number changed. - At least 2 GB of RAM for a lightly loaded server. Memory and CPU use grow with the amount of traffic Zeek has to analyze.
- Free disk space for logs. A busy interface produces a lot of log data.
Step 1: Update the system and find the interface name
Bring the system up to date:
sudo dnf upgrade --refresh
Reboot if a new kernel was installed. Then list the network interfaces so you know which one Zeek should monitor:
ip -br addr
On a typical VPS the public interface is called something like eth0, ens3 or enp1s0. The examples below use ens3.
Step 2: Add the Zeek package repository
The Zeek project builds its Linux packages on the openSUSE Build Service. Download the repository definition for Fedora 44 into /etc/yum.repos.d/:
sudo curl -fsSL -o /etc/yum.repos.d/security-zeek.repo \
'https://download.opensuse.org/repositories/security:/zeek/Fedora_44/security:zeek.repo'
The file enables signature checking (gpgcheck=1) and points to the repository's signing key, so dnf asks you to accept that key the first time you install from it. You can read the file before going on:
cat /etc/yum.repos.d/security-zeek.repo
Step 3: Install Zeek
The repository carries several package lines:
| Package | What you get |
|---|---|
zeek-9.0 | The 9.0 long-term-support line (9.0.1 in November 2026). Stays on 9.0.x. |
zeek-8.0 | The previous LTS line. |
zeek | The latest Zeek release, whatever line it belongs to. |
zeek-rc, zeek-nightly | Release candidates and nightly builds, for testing only. |
The older zeek-lts package is still visible in the repository, but the project documentation describes it as no longer supported; use a versioned LTS package instead. Install the 9.0 line:
sudo dnf install zeek-9.0
Check the key that dnf shows, confirm, and let the installation finish. The packages install everything under /opt/zeek: programs in /opt/zeek/bin, configuration in /opt/zeek/etc, your site scripts in /opt/zeek/share/zeek/site and logs in /opt/zeek/logs.
/opt/zeek/bin is not on the default search path. Add it for login shells:
echo 'export PATH=$PATH:/opt/zeek/bin' | sudo tee /etc/profile.d/zeek.sh
Log out and back in, then confirm the version:
zeek --version
Because sudo uses its own restricted search path, the commands below call ZeekControl by its full path.
Step 4: Configure the sensor
ZeekControl reads three files in /opt/zeek/etc.
node.cfg: what to run and where
Open the file:
sudo nano /opt/zeek/etc/node.cfg
For a single server, keep the standalone section and set interface to the name you found in step 1:
[zeek]
type=standalone
host=localhost
interface=ens3
networks.cfg: which addresses are local
This file lists your own networks in CIDR notation, one per line, with an optional description. Zeek uses it to tell local hosts from remote ones (the Site::local_nets setting). Replace the example ranges with the networks your server actually belongs to:
sudo nano /opt/zeek/etc/networks.cfg
203.0.113.0/24 Public network of this server
10.0.0.0/8 Private address space
zeekctl.cfg: ZeekControl options
The defaults work as they are. The option you are most likely to change is MailTo, the address that receives reports about crashes and other problems; LogExpireInterval controls how long archived logs are kept.
sudo nano /opt/zeek/etc/zeekctl.cfg
Step 5: Deploy and start Zeek
The deploy command checks the configuration and scripts, installs them and starts the node:
sudo /opt/zeek/bin/zeekctl deploy
Check that the node is running:
sudo /opt/zeek/bin/zeekctl status
The status column should read running. If it says crashed, ask ZeekControl for the reason:
sudo /opt/zeek/bin/zeekctl diag
A wrong interface name in node.cfg is the most common cause.
Step 6: Look at the logs
While Zeek runs, it writes its current logs to /opt/zeek/logs/current:
sudo ls -l /opt/zeek/logs/current
Follow the connection log and generate some traffic, for example by opening a new SSH session to the server or running curl https://example.com on it:
sudo tail -f /opt/zeek/logs/current/conn.log
A connection is written to conn.log when it ends, so entries appear with a short delay. Other files such as dns.log, ssl.log, http.log and notice.log appear as soon as Zeek sees matching traffic.
Logs are rotated once per hour by default and whenever Zeek is stopped. Rotated logs are compressed and moved to a directory named after the date, such as /opt/zeek/logs/2026-11-15/. Read them without unpacking:
sudo sh -c 'zcat /opt/zeek/logs/2026-11-15/conn.*.log.gz' | less
Keeping Zeek running
Apply changes with deploy
Nothing you change takes effect until you run deploy again. That applies to the three configuration files, to your own scripts in /opt/zeek/share/zeek/site/local.zeek (a file that package upgrades do not overwrite) and to upgrades of Zeek itself:
sudo /opt/zeek/bin/zeekctl deploy
To stop monitoring, run sudo /opt/zeek/bin/zeekctl stop.
Restart crashed nodes automatically
ZeekControl has a cron command that restarts crashed nodes and does housekeeping such as expiring old logs. The project recommends running it every five minutes as the same user that runs zeekctl. Fedora no longer installs a cron daemon by default, so add one first:
sudo dnf install cronie
sudo systemctl enable --now crond
sudo crontab -e
Add this line:
*/5 * * * * /opt/zeek/bin/zeekctl cron
Updates
New 9.0.x releases arrive through the normal sudo dnf upgrade. Run zeekctl deploy afterwards. When you upgrade Fedora itself, replace the release number in /etc/yum.repos.d/security-zeek.repo after checking that the project publishes a repository for the new release.
The Zeek installation documentation and the quick start guide describe the other installation routes and the next steps with ZeekControl.
Frequently asked questions
Do my old Bro scripts and commands still work?
Not unchanged. With Zeek 3.0 the binaries, many script names and some events were renamed, and script files now end in .zeek instead of .bro. broctl became zeekctl and local.bro became local.zeek. Scripts written for Bro 2.x usually need to be ported.
Can I install Zeek the same way on AlmaLinux or Rocky Linux?
As of November 2026 the project's repository has package directories for Fedora, Debian, Ubuntu, Raspbian and openSUSE, but none for the RHEL family. On those systems use the official container image (docker pull zeek/zeek:lts) or build Zeek from source.
Does Zeek block attacks?
No. Zeek only observes traffic and records what it sees. Its value is the detailed log trail and the notices its scripts raise, which you can search yourself or forward to a log platform or SIEM. To drop traffic you need a firewall or an inline intrusion prevention system next to it.
Does Zeek see traffic of other servers in my network?
Only if that traffic reaches the monitored interface. On a VPS that normally means the server's own traffic. To watch a whole network you need a mirror (SPAN) port or a network tap feeding the sensor.