vastcookie.blogg.se - Remote wake up pc

#Remote wake up pc install#

NetworkManager provides Wake-on-LAN ethernet support. etc/netctl/ profile ExecUpPost='/usr/bin/ethtool -s interface wol g' NetworkManager If using netctl, one can make this setting persistent by adding the following the netctl profile: First, make sure cron is enabled, and then edit a crontab for the root user that contains the following /usr/bin/ethtool -s interface wol g The $name placeholder will be replaced by the value of the NAME variable for the matched device.Ī command can be run each time the computer is (re)booted using in a crontab. etc/udev/rules.d/ les ACTION="add", SUBSYSTEM="net", NAME="enp*", RUN+="/usr/bin/ethtool -s $name wol g"

Otherwise, NAME would be undefined and the rule would not run. The file name is important and must start with a number between 81 and 99 so that it runs after les, which renames interfaces with predictable names. The following rule will turn on WOL on all network interfaces whose name matches enp*. Udev is capable of running any command as soon as a device is visible.

#Remote wake up pc install#

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.