Join a WPA2-Enterprise (802.1X) network like eduroam from the command line
Checked the whole command against man 5 nm-settings-nmcli and man 1 nmcli from networkmanager 1.58.1-1 on this machine, then executed the record's exact command under nmcli --offline, which builds the keyfile on stdout and never contacts the daemon. It is valid and produces a correct profile, so every property name holds for 1.58: wifi-sec.key-mgmt wpa-eap, 802-1x.eap peap, 802-1x.phase2-auth mschapv2, 802-1x.identity, 802-1x.anonymous-identity, 802-1x.password, 802-1x.ca-cert, 802-1x.domain-suffix-match, and the -- separator. man 1 nmcli states that nmcli accepts wifi-sec in place of 802-11-wireless-security. The man page describes phase2-auth under PEAP as selecting from gtc, otp, md5 and tls, which reads as excluding mschapv2, but the combined valid-values list includes it and Omarchy 4 itself ships exactly this pairing, so the record is right and the man prose is incomplete.
Three defects, all confirmed on this machine rather than inferred. First, the symptom claim that the GUI "only asks for a password" is false on Omarchy 4. /usr/share/omarchy/shell/plugins/panels/network/Panel.qml computes isEnterprise at line 1604 and shows a field with placeholderText: "Identity (user@domain)" at line 1848, and /usr/share/omarchy/shell/plugins/panels/network/Model.js lines 319 to 326 hold enterpriseConnectScript, which runs nmcli connection add ... wifi-sec.key-mgmt wpa-eap 802-1x.eap peap 802-1x.phase2-auth mschapv2 802-1x.identity "$2". Second, the cause is Omarchy 3 framing and contains a factual error: impala and iwctl drive iwd, not wpa_supplicant, so "wpa_supplicant has nothing to authenticate with" is wrong for those tools. Omarchy 4 ships neither. install/hardware/network.sh on the quattro branch runs systemctl disable iwd.service, pacman -Q iwd impala reports both absent here, systemctl is-enabled iwd returns not-found, nothing under /usr/share/omarchy mentions impala, and wpa_supplicant is the running supplicant (pid 1624). Third, ifname wlan0 and ip addr show wlan0 are wrong. Predictable naming is active (no net.ifnames=0 in /proc/cmdline, no .link file and no 80-net-setup-link.rules override) and the card here is wlo1 on iwlwifi. The offline run showed the record's command baking interface-name=wlan0 into the keyfile, which would pin the profile to a nonexistent device. Omarchy's own script omits ifname, and an offline run without it emits no interface-name line.
Two additions to danger, both genuine. Omarchy 4's own enterprise path sets no CA certificate and no domain-suffix-match, so the record's warning understates the situation by treating omission as the reader's mistake when it is the shipped default. And the record passes the password as an nmcli argument, which Omarchy explicitly avoids: the comment at Model.js lines 315 to 318 says "argv is world-readable in /proc, so the secret must never be an argument" and pipes it through nmcli connection edit instead. The corrected fix adopts that pattern. 802-1x.ca-cert is documented as "This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended", which backs the record's original instinct.
Sources. Both cited basecamp/omarchy issue URLs are hard 404s under curl with no redirect, so they are removed and replaced with the omacom equivalents. Read both in full: #2382 is the impala WPA2-Enterprise report the symptom quotes, and #7257 is the Quickshell panel showing an enterprise connection as NOT CONNECTED. #7257 is still open with no comments as of 2026-09-11, against a newest tag of v4.0.3, so that half of the symptom is a live Omarchy 4 bug. NetworkManager.conf.5 is removed: it resolves but documents the daemon config file and says nothing about 802-1x connection properties, so it never supported the claim. nm-settings-nmcli.5 and nmcli.1 replace it.
Not exercised. No enterprise SSID is reachable from this workstation and I was instructed not to add a connection or use sudo, so association and EAP authentication were never performed. The Wi-Fi card wlo1 is present and unblocked in rfkill but sits disconnected because the machine is on ethernet eno2. Everything above is either read from a local file, read from the upstream quattro branch, or produced by nmcli --offline, which alters nothing. The claim that the corrected fix successfully authenticates against a real RADIUS server is untested.
An 802.1X profile with no 802-1x.ca-cert and no 802-1x.domain-suffix-match trusts any RADIUS server that presents a certificate, which is all an attacker needs to harvest the credentials from a spoofed SSID. Set both. This is not hypothetical on Omarchy 4: the bar panel's own enterprise connect path sets neither, so a profile created from the GUI needs both added afterwards. Putting the password on an nmcli command line is a second exposure, because /proc/<pid>/cmdline is world readable while the command runs and the line also enters shell history. Set the secret over stdin with nmcli connection edit. Prefer the CA your institution publishes over /etc/ssl/certs/ca-certificates.crt, because the system bundle lets any publicly trusted CA vouch for the RADIUS server and 802-1x.domain-suffix-match is then the only thing standing between you and a mis-issued certificate.
Symptom
University or corporate Wi-Fi either cannot be joined or joins and then reports itself wrong. With impala or iwctl the picker offers only a password field and the enterprise network never associates, which is what "impala can't connect to school wifi using WPA2 enterprise 802.1X" describes. On Omarchy 4 the bar panel does ask for an identity, so the failures look different. The profile it creates performs no server certificate check at all, and the panel can go on showing a working enterprise connection as NOT CONNECTED while nmcli reports it activated and the IP address, gateway, ping and traffic figures on that same panel are all correct.
Cause
Two different causes, and Omarchy 4 changed which one applies.
With impala or iwctl, the Omarchy 3 default, the TUI does not expose the fields an enterprise network needs, which are the EAP method, the phase 2 inner auth, the identity, the anonymous identity and the CA certificate. Those tools drive **iwd**, not wpa_supplicant, and iwd expects an 802.1X network to be described by a provisioning file it reads from /var/lib/iwd rather than by credentials entered at a prompt.
Omarchy 4 does not use iwd at all. Its hardware setup runs systemctl disable iwd.service and the stack is NetworkManager driving wpa_supplicant. Its bar panel does detect an enterprise SSID and does ask for an identity, then builds a PEAP/MSCHAPv2 profile. What it does not set is 802-1x.ca-cert or 802-1x.domain-suffix-match, so the profile it writes accepts any RADIUS server that answers. Separately, the panel's connected indicator misreads an active 802.1X profile and can display NOT CONNECTED for a connection NetworkManager considers activated. That second one is cosmetic and does not affect traffic.
Fix
Build the profile with nmcli so every 802.1X field is set explicitly.
Leave ifname out. Predictable interface naming is on by default, so the device is normally wlo1 or wlp3s0 and almost never wlan0. Passing a name that does not exist bakes interface-name= into the profile and it will never activate. Check what you actually have:
nmcli -f DEVICE,TYPE device status | grep wifi
PEAP with MSCHAPv2 is the common case, eduroam included:
sudo nmcli connection add type wifi con-name eduroam ssid "eduroam" \
wifi-sec.key-mgmt wpa-eap \
802-1x.eap peap \
802-1x.phase2-auth mschapv2 \
802-1x.identity "you@uni.edu" \
802-1x.anonymous-identity "anonymous@uni.edu" \
802-1x.ca-cert /etc/ssl/certs/ca-certificates.crt \
802-1x.domain-suffix-match "radius.uni.edu"
Set the password separately, not on that command line. /proc/<pid>/cmdline is world readable for the life of the process, and the line lands in shell history too. read and printf are both bash builtins, so with this form the secret never becomes an argument to any process:
read -rs -p 'EAP password: ' pw
printf 'set 802-1x.password %s\nsave\nquit\n' "$pw" \
| sudo nmcli connection edit eduroam
unset pw
sudo nmcli connection up eduroam
For TTLS with PAP instead:
sudo nmcli connection modify eduroam 802-1x.eap ttls 802-1x.phase2-auth pap
sudo nmcli connection up eduroam
Most institutions publish their own RADIUS CA and hostname. Use that CA file rather than the whole system bundle where one is offered:
sudo nmcli connection modify eduroam \
802-1x.ca-cert /etc/ssl/certs/your-institution-ca.pem
Watch the authentication if it fails:
journalctl -u NetworkManager -u wpa_supplicant -f
**Omarchy 4.** The bar panel (Super + Ctrl + W) does detect an enterprise SSID and offer an identity field, so you can join from the GUI. It builds a PEAP/MSCHAPv2 profile and sets neither 802-1x.ca-cert nor 802-1x.domain-suffix-match, so add both to whatever profile it left behind:
sudo nmcli connection modify "<ssid>" \
802-1x.ca-cert /etc/ssl/certs/ca-certificates.crt \
802-1x.domain-suffix-match "radius.uni.edu"
sudo nmcli connection up "<ssid>"
If that panel keeps showing NOT CONNECTED while nmcli reports the connection activated, the link is fine and the indicator is wrong. Trust nmcli.
**Omarchy 3, or any install using impala or iwctl.** Those drive iwd, which wants a provisioning file under /var/lib/iwd/<ssid>.8021x rather than credentials typed at a prompt. Switch to NetworkManager and use the commands above, which is the route Omarchy 4 took.
Verify
nmcli -f GENERAL.STATE connection show eduroam reports activated and ip addr show <device> has an address. Take the device name from nmcli -f DEVICE,TYPE device status | grep wifi rather than assuming wlan0. nmcli -f 802-1x connection show eduroam lists the EAP settings, and both 802-1x.ca-cert and 802-1x.domain-suffix-match must be non-empty there. On Omarchy 4 ignore the bar panel's connected indicator for this check and trust nmcli.
Sources
- https://github.com/omacom/omarchy/issues/2382
- https://github.com/omacom/omarchy/issues/7257
- https://man.archlinux.org/man/nm-settings-nmcli.5
- https://man.archlinux.org/man/nmcli.1
- https://github.com/omacom/omarchy/blob/quattro/shell/plugins/panels/network/Model.js
- https://github.com/omacom/omarchy/blob/quattro/shell/plugins/panels/network/Panel.qml
- https://github.com/omacom/omarchy/blob/quattro/install/hardware/network.sh
- https://wiki.archlinux.org/title/NetworkManager
- https://github.com/omacom/omarchy/issues/11791