OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network low occasional DISPUTE

Wake-on-LAN does not survive a reboot until the NetworkManager profile requests it

omarchyarchendeavouroscachyosmanjaronetworkmanagerdesktopethernet
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The first pass rewrote title and cause, and both now hold. NetworkManager's wake_on_lan_enable() in nm-device-ethernet.c falls back from the profile's default to the global ethernet.wake-on-lan, and with that unset it uses NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE, so it leaves the driver's setting alone. The local nm-settings-nmcli(5) on NetworkManager 1.58.1 documents default as "use global settings". The fix matches the Arch wiki Wake-on-LAN NetworkManager section and its 'still powered off on shutdown' auto-negotiate note. ethtool 7.1 is in extra and not installed here, wol 0.7.1 is in extra and wakeonlan is in neither core nor extra. One defect: the verify step ran wol <MAC> bare, and the Arch wiki says wol defaults to port 40000 and needs -p 9. Verify corrected. Not exercised: no NIC was changed.

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

Wake-on-LAN keeps the NIC powered after shutdown. On laptops this drains the battery while the machine is off. Some motherboards also wake at random with BIOS WoL enabled.

Symptom

Wake-on-LAN is enabled in the BIOS and ethtool -s enp3s0 wol g was run, yet the machine never wakes from a magic packet. The link lights on the switch go dark at shutdown. sudo ethtool enp3s0 | grep Wake-on shows Supports Wake-on: pumbg but Wake-on: d after a reboot.

Cause

The NIC's wake setting is not persistent. Many drivers start with Wake-on: d, and a one-off ethtool -s <iface> wol g is lost at the next boot. NetworkManager only arms Wake-on-LAN when the connection profile asks for it. The profile default for 802-3-ethernet.wake-on-lan is default, which defers to a global ethernet.wake-on-lan in NetworkManager.conf, and with none set NetworkManager leaves the driver's d in place. Setting the profile to magic makes NetworkManager program magic-packet wake each time it activates the link. Omarchy 4 manages ethernet with NetworkManager and does not install ethtool.

Fix

Find the wired profile and turn on magic-packet wake in it:


nmcli connection show
nmcli connection show 'Wired connection 1' | grep 802-3-ethernet.wake-on-lan
sudo nmcli connection modify 'Wired connection 1' 802-3-ethernet.wake-on-lan magic
nmcli connection up 'Wired connection 1'

If the adapter still powers off at shutdown, the Arch wiki suggests also forcing auto-negotiation:


sudo nmcli connection modify 'Wired connection 1' 802-3-ethernet.auto-negotiate yes

Check the result with ethtool:


sudo pacman -S --needed ethtool
sudo ethtool enp3s0 | grep Wake-on      # want: Wake-on: g

The BIOS or UEFI option (often "Wake on LAN", "Power on by PCI-E", or "Deep Sleep: off") must also be enabled.

Verify

After a reboot, sudo ethtool <iface> | grep Wake-on reads Wake-on: g. Shut down, then from another machine on the same network run wol -p 9 <MAC> (wol from extra, which defaults to port 40000) or wakeonlan <MAC> (AUR), and the machine powers on.

Sources

wake-on-lan-reset-by-networkmanager