This layer contains parallel capabilities: NetworkManager manages Wi-Fi and Ethernet, BlueZ manages Bluetooth, Avahi discovers local services, and UFW manages host traffic policy. They are neither sequential installation steps nor replacements for one another.
Example: a network printer. NetworkManager establishes connectivity. On a compatible network and device, Avahi helps discover printing services. CUPS then handles queues and jobs. Firewall and network-isolation policies can still affect communication; discovery does not guarantee delivery.
Example: a Bluetooth headset. BlueZ handles discovery, pairing and connection, while PipeWire and WirePlumber provide audio processing and routing. Connecting to Wi-Fi is generally not a prerequisite.
Failure to connect to Wi-Fi, failure to discover a local service, and a connected but silent headset therefore follow different paths. Firewall rules cannot replace connection management or fix undetected wireless hardware.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
Manages Wi-Fi and Ethernet connections; the network panel is its user-facing entry point.
Package
networkmanager
Membership
Core manifest
Omarchy configuration or entry point
Super + Ctrl + W
Purpose and everyday use
Manages wired and wireless connection profiles, addressing and connection state. The Omarchy network panel is a convenient front end for everyday Wi-Fi use.
How it works and connects
Separates network devices from saved connection profiles. A device being connected does not guarantee routing or DNS works. The pinned Omarchy setup enables NetworkManager and retires competing legacy networkd configuration.
Configuration and customization
Use the network panel, nmtui or nmcli for profiles. Review addresses, DNS and autoconnect separately; changing one profile need not require replacing global configuration.
Troubleshooting approach
Inspect device status, then address/route information and DNS. If no Wi-Fi device exists, investigate hardware, firmware and radio state before editing a connection profile.
Limits and change considerations
Profiles and diagnostic output can contain identifying network information. Do not run competing managers on one interface or share saved credentials in support reports.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi networkmanager
nmcli device status
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Linux Bluetooth stack; pairing and audio involve other desktop and sound components too.
Package
bluez
Membership
Core manifest
Purpose and everyday use
Provides Linux Bluetooth support for controllers and paired devices. Use it to understand discovery, pairing and connection before investigating application-level functions.
How it works and connects
The daemon exposes Bluetooth interfaces over D-Bus. Desktop panels and bluetoothctl act as clients. Headset audio also depends on PipeWire and WirePlumber.
Configuration and customization
Use the desktop panel for ordinary pairing. Controller power, device trust and audio profile selection are separate decisions, not one universal Bluetooth switch.
Troubleshooting approach
Check controller visibility and power first, then pairing and connection status. If only sound fails, inspect the audio route instead of immediately deleting the pairing.
Limits and change considerations
Removing a pairing discards stored trust and requires pairing again. Discoverability exposes the device locally; enable it only when needed for your workflow.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi bluez
bluetoothctl show
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Local network service discovery using mDNS/DNS-SD.
Package
avahi
Membership
Core manifest
Purpose and everyday use
Discovers local services such as compatible printers using mDNS/DNS-SD. It helps applications find nearby services without manually entering every address.
How it works and connects
Discovery uses local multicast and service announcements. NetworkManager provides connectivity, while applications such as printing tools consume the discovered services.
Configuration and customization
Review daemon settings when choosing interfaces or published services. Start with the existing distribution setup; publishing a service and merely discovering one are distinct roles.
Troubleshooting approach
Check that devices share a suitable network and that guest-network isolation or multicast filtering is not blocking discovery. Internet DNS changes rarely solve local discovery problems.
Limits and change considerations
It is not an internet DNS server or a file-sharing server. Service names and announcements can disclose information to other devices on the local network.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi avahi
systemctl status avahi-daemon --no-pager
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Host firewall management; firewall policy is separate from Wi-Fi connectivity.
Package
ufw
Membership
Core manifest
Purpose and everyday use
Manages host firewall policy through a simpler command interface. Use it to reason about which incoming or forwarded traffic should be permitted.
How it works and connects
Translates policy into the Linux packet-filtering stack. Containers can introduce their own networking rules, so Docker traffic requires separate consideration.
Configuration and customization
Review current policy before adding service-specific rules. Record the intended port, protocol, source and direction rather than adding broad exceptions.
Troubleshooting approach
First confirm that the application is listening and the route works. A firewall exception cannot start a stopped server or repair DNS.
Limits and change considerations
Remote-access rule changes can interrupt your management connection. Avoid disabling all protection as a routine connectivity test.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi ufw
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.