Udev is capable of running any command as soon as a device is visible. This is an equivalent of previous systemd.link option, but uses a standalone systemd Īlternatively install the wol-systemd AUR package, then activate this new service by starting rvice.

In the Match section, OriginalName= can also be used to identify the interface.

This configuration applies only to the link-level, and is independent of network-level daemons such as NetworkManager or systemd-networkd.

To be considered, the file name should alphabetically come before the default 99-default.link.

The content of the default link file /usr/lib/systemd/network/99-default.link shipped with systemd has to be included, otherwise the interface might be misconfigured.

Only the first matching file is is applied.

The value g is required for WoL to work, if not, the following command enables the WoL feature in the driver: The Wake-on values define what activity triggers wake up: d (disabled), p (PHY activity), u (unicast activity), m (multicast activity), b (broadcast activity), a (ARP activity), and g (magic packet activity). # ethtool interface | grep Wake-on Supports Wake-on: pumbag To query this status or to change the settings, install ethtool, determine the name of the network interface, and query it using the command: Software configuration Enable WoL on the network adapterĭepending on the hardware, the network driver may have WoL switched off by default. Note that some motherboards are affected by a bug that can cause immediate or random #Wake-up after shutdown whenever the BIOS WoL feature is enabled. Look for terminology such as 'PCI Power up', 'Allow PCI wake up event' or 'Boot from PCI/PCI-E'. Different motherboard manufacturers use slightly different language for this feature.

The Wake-on-LAN feature also has to be enabled in the computer's BIOS.

Some wireless cards have support for Wake on Wireless (WoWLAN or WoW). The target computer has to be physically connected (with a cable) to a router or to the source computer for WoL to work properly. The target computer's motherboard and Network Interface Controller have to support Wake-on-LAN. 5.1.1 Network adapter is still powered off on shutdown.4.1 Check reception of the magic packets.

Teamviewer wake on lan tutorial