OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium common DISPUTE

Reconnect after an interface rename orphans your NetworkManager profile

omarchyarchendeavouroscachyosmanjarolaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Re-checked every load-bearing specific on this Omarchy 4 workstation (omarchy 4.0.2-1, networkmanager 1.58.1-1, systemd 261.2-1-arch, kernel 7.1.9) and against the current man pages and wiki. Most of the record holds and I kept it. Confirmed on this machine: the error string is in the shipped 1.58 binary verbatim, strings /usr/bin/NetworkManager yields both Connection '%s' is not available on device %s because %s and profile is not compatible with device (%s). man 5 systemd.link states the first link file in lexicographic order wins and that a user file must sort before 99-default.link, and PermanentMACAddress= is a real Match key. The Arch Iwd wiki reproduces /usr/lib/systemd/network/80-iwd.link with NamePolicy=keep kernel and the identical ln -s /dev/null mask. systemd issue 33347 is real and says what the record claims, enp5s0 to enp7s0 on Arch after a GPU swap. Network_configuration confirms the sort rule, the PermanentMACAddress= example, udevadm trigger --verbose --subsystem-match=net --action=add, udevadm test-builtin net_setup_link and its own accuracy flag behind the danger note. nmcli syntax is current for 1.58 and I verified it without touching anything, using nmcli --offline connection modify on a scratch keyfile: connection.interface-name "" removes the key (man nmcli confirms an empty value resets a property) and 802-11-wireless.mac-address is accepted, while 802-3-ethernet.mac-address is correctly rejected on a wifi profile, so the record's wired and wireless branching is right. All four diagnostics and all three verify commands ran here. Two real defects. (1) The fix said to get the permanent address from ip -br link or ethtool -P <iface>. Both are wrong on Omarchy 4. ip -br link prints the CURRENT address, and on Wi-Fi that is usually the randomized scan address, which is exactly the value the record warns against: ip -br link here shows wlo1 as fe:86:ef:5b:7e:d4 while ip -d link show wlo1 shows permaddr 3c:6a:a7:68:5c:5e. Following the record as written would pin a throwaway MAC. And ethtool is not installed on Omarchy 4, confirmed that /usr/bin/ethtool does not exist and no package owns it. (2) The cause overgeneralised, saying predictable names are derived from PCI topology. True for enp*/wlp*, but both NICs here are onboard-named (eno2, wlo1) from ID_NET_NAME_ONBOARD under naming scheme v261, which does not move when a PCIe device is added. Added, because it answers whether the fix is even needed: 99-default.link sets AlternativeNamesPolicy=database onboard slot path mac, so the other candidate names are registered as kernel altnames (ip -d link show wlo1 lists altname wlp0s20f3 and altname wlx3c6aa7685c5e) and ip still accepts the old name after a policy change, which masks the problem. The NetworkManager profile is what stops matching. Likely, not confirmed: NetworkManager 1.58 does not resolve altnames for connection.interface-name, since strings on /usr/bin/NetworkManager finds no altname literal and neither man page mentions altnames. Confirming that needs an actual rename on a test VM. Also labelled the Omarchy 4 branch, confirmed: /etc/systemd/network/ is empty, no Omarchy package ships a .link file (omarchy-settings ships only /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf), iwd is not installed, and udevadm info reports ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link for both NICs, so nothing in the distribution renames interfaces. Omarchy 3 did ship iwd, which dhh's closing comment on omacom/omarchy issue 4607 confirms Quattro replaced with NetworkManager. All four cited URLs resolve and support their claims, so nothing is removed. NOT exercised: no rename was induced and no profile was modified, added or deleted, because this is a live workstation. The repair steps themselves are unexercised and rest on the 1.58 documentation plus the offline syntax checks. severity and frequency unchanged.

The cause above was rewritten on 2026-09-11 to match this note; the fix was corrected by the audit itself.
RISK

Renaming an interface with a custom .link file means 99-default.link no longer applies to that device, because only the first matching .link file is used, so every other property it would have set is lost, including MACAddressPolicy=persistent and AlternativeNamesPolicy=. The Arch wiki carries its own accuracy flag on exactly this point. If you rename a device that firewall rules or a wg-quick config refer to by name, those rules silently stop matching, so grep for the old name across /etc before you commit:


sudo grep -rn '<oldname>' /etc/ --include='*.conf' --include='*.rules' --include='fstab'

Every repair here interrupts the link. nmcli connection up, udevadm trigger and the reboot in the iwd branch all drop the interface, so do not run them against the NIC carrying your only route while you are logged in over it. Clearing connection.interface-name on a machine with more than one NIC of the same type lets the profile bind to whichever device activates first, which can put the wrong network on the wrong interface. Pin the MAC in that case rather than unpinning the name.

Symptom

After an update, a BIOS change, or plugging in a new PCIe/NVMe card, the network no longer comes up on its own. The saved connection is still listed by nmcli connection show but never activates, and nmcli connection up "<name>" fails with Connection '<name>' is not available on device <iface> because profile is not compatible with device. ip link shows an interface with a *different* name than before: wlan0 where you had wlp3s0, or enp4s0 where you had enp3s0, or wwp0s20f0u3 where you had enp0s20f0u3.

Cause

NetworkManager profiles can be pinned to a device by connection.interface-name. The 1.58 documentation for that property says setting it restricts the interfaces a connection can be used with, and that if interface names change or are reordered the connection may be applied to the wrong interface. When the name it names no longer exists, the profile becomes unusable. Renames happen for several ordinary reasons. Path-derived names such as enp3s0 and wlp3s0 come from PCI topology, so adding or removing a PCIe device can make the firmware renumber the bus (systemd issue 33347 reports enp5s0 becoming enp7s0 on Arch after a GPU swap). Onboard names such as eno2 and wlo1 come from a firmware-supplied index instead, so they survive PCIe changes but move if the firmware changes that index. A .link file shipped by a package can change the policy outright: installing iwd alone is enough, because it ships /usr/lib/systemd/network/80-iwd.link with NamePolicy=keep kernel, which sorts before 99-default.link and therefore wins for all wlan interfaces and leaves them as wlan0. And a kernel change can reclassify a device into a different prefix entirely.

One thing masks the problem. 99-default.link also sets AlternativeNamesPolicy=database onboard slot path mac, so every other candidate name is registered as a kernel alternative name and ip still accepts the old name after the primary name changes. The tooling looks fine. It is the NetworkManager profile that stops matching.

On Omarchy 4 nothing in the distribution renames interfaces: /etc/systemd/network/ is empty, no Omarchy package ships a .link file, iwd is not installed, and both NICs resolve to /usr/lib/systemd/network/99-default.link. Omarchy 3 shipped iwd, which Omarchy 4 replaced with NetworkManager and wpa_supplicant, so the iwd branch below only applies if you installed it yourself.

Fix

Establish what changed:


ip -br link
nmcli -f NAME,UUID,TYPE,DEVICE connection show
grep -r 'interface-name' /etc/NetworkManager/system-connections/
ls -l /usr/lib/systemd/network/*.link /etc/systemd/network/*.link 2>/dev/null
udevadm info /sys/class/net/<iface> | grep -E 'ID_NET_NAME|ID_NET_LINK_FILE|ID_NET_NAMING_SCHEME'
udevadm test-builtin net_setup_link /sys/class/net/<iface>

ID_NET_LINK_FILE tells you which .link file actually won, which is the decisive fact.

**Quickest fix, unpin the profile** so it binds to whatever device of the right type is present:


nmcli connection modify "<name>" connection.interface-name ""
nmcli connection up "<name>"

**Better for machines with more than one NIC, pin to the MAC instead of the name**, which survives every rename:


# wired
nmcli connection modify "<name>" 802-3-ethernet.mac-address AA:BB:CC:DD:EE:FF
# wireless
nmcli connection modify "<name>" 802-11-wireless.mac-address AA:BB:CC:DD:EE:FF
nmcli connection modify "<name>" connection.interface-name ""

Get the permanent address with ip -d link show <iface>, which prints it as permaddr:


ip -d link show wlo1 | grep -o 'permaddr [0-9a-f:]*'

Do not read it from ip -br link or plain ip link. Those show the *current* address, and on Wi-Fi that is usually the randomized scan address, which is the one you must not pin. ethtool -P also works but ethtool is not installed on Omarchy 4.

**Or nail the name down** so it never moves again. A .link file ordered before 99-default.link, because only the first matching file is applied:


# /etc/systemd/network/10-net0.link
[Match]
PermanentMACAddress=aa:bb:cc:dd:ee:ff

[Link]
Name=net0

sudo udevadm trigger --verbose --subsystem-match=net --action=add

**If installing iwd renamed your wireless interface** and you would rather keep predictable names, mask its link file. Omarchy 4 does not ship iwd, so this only applies if you installed it:


sudo ln -s /dev/null /etc/systemd/network/80-iwd.link
sudo reboot

After any of these, update anything else that referenced the old name: /etc/fstab _netdev mounts, firewall rules (ufw status numbered), wg-quick PostUp lines, and systemd-networkd [Match] Name= stanzas.

Verify

nmcli -f NAME,DEVICE connection show --active shows the profile bound to the current interface. ip -br addr shows an address on it. Reboot once and confirm it comes up unattended.

Sources

interface-renamed-orphans-networkmanager-profile