Install IbexWall
Esta página aún no está disponible en tu idioma.
Supported distributions
Section titled “Supported distributions”IbexWall is tested in virtual machines on Fedora, Ubuntu 24.04, Ubuntu 26.04, Debian and Arch Linux. Distributions based on them, such as EndeavourOS or Omarchy on the Arch side, should work but are checked by hand rather than in the test matrix.
IbexWall needs systemd, polkit and nftables. The packages depend on them, so your package manager installs them if they are missing.
The packages
Section titled “The packages”IbexWall comes as three packages on every family, and one optional fourth.
ibexwall: the daemon (ibexwalld), the command line (ibexctl), the secure DNS resolver, the plugins, the systemd units, the polkit policy and the users it needs.ibexwall-desktop: the window, the tray icon and the session agent that shows notifications. It depends onibexwallat the same version, and on GTK 3 and WebKitGTK 4.1.ibexwall-mcp: the server that lets an AI assistant read your status. You only need it if you plan to use Connect an AI.ibexwall-apparmoron Debian and Ubuntu, oribexwall-selinuxon Fedora: policies that confine the resolver, the MCP server and the plugins. Arch ships neither.
Recommended but not required: chrony (for the secure time plugin), and firewalld or ufw (for the firewall screen to drive the firewall you already use).
Fedora
Section titled “Fedora”Download the packages from the release, then install them from the folder you saved them in.
sudo dnf install ./ibexwall-*.rpmThis installs everything in the folder, including ibexwall-selinux. If you only want some of them, name the files instead of using the wildcard.
Ubuntu and Debian
Section titled “Ubuntu and Debian”sudo apt install ./ibexwall_*.deb ./ibexwall-desktop_*.deb ./ibexwall-apparmor_*.debAdd ./ibexwall-mcp_*.deb if you want the assistant server. Giving apt the file paths lets it fetch the dependencies from your normal repositories.
Arch Linux
Section titled “Arch Linux”sudo pacman -U ibexwall-*.pkg.tar.zstAs on Fedora, name the files if you do not want all of them.
What the install switches on
Section titled “What the install switches on”The install only creates users and directories, and switches on sockets: the control socket (/run/ibexwall/core.sock) and one socket per plugin. A socket costs nothing until something connects to it, and systemd then starts the program behind it.
The install applies no IbexWall change. Your firewall, DNS, kernel settings and units are as they were. Every change still needs a plan and your approval. The secure DNS resolver, the connection monitor, the MCP server and the session agent stay off until used.
Start the app
Section titled “Start the app”Open IbexWall from your application menu, or run:
ibexwall-desktopWithout the desktop package you can use the command line. ibexctl status shows that the daemon answers, and ibexctl tui opens a terminal interface. See the command line.
Verify a download
Section titled “Verify a download”Releases carry checksums, signatures, a software bill of materials and a provenance statement. Check them before you install. The steps are in Release verification.
Upgrade
Section titled “Upgrade”Install the newer packages the same way you installed the first ones. The upgrade restarts the daemon and the plugin services on the new files. The changes you made, your History and your firewall rules stay.
To remove IbexWall, see Uninstall.